41
Views
3
Comments
[OAuth2 Provider] Circular dependency in main component
oauth2-provider
Web icon
Forge asset by Barduino
Application Type
Traditional Web

There is a circular dependency between OAuth2 and OAuth2_CrossTenant. This is throwing all sorts of errors in Architecture Dashboard.

Can this be solved? 

2023-09-13 13-47-19
Nuno Magalhães

Hello,

You're right. This module has circular dependencies. If you want you can solve it by yourself. If your tables have already data use this solution:
https://learn.outsystems.com/training/journeys/refactoring-apps-414/extracting-elements-without-impacting-consumers-/o11/732

If not you can always put the tables in a new module OAuth2_CS and create the CRUD actions. It will take some time and if the component updates you'll lose this structure.

2020-09-21 08-42-47
Vincent Koning

Yeah. I know I can fix it myself but I would rather have that the component itself gets updated so that everyone benefits from this. 

2019-07-08 11-04-35
Leonardo Fernandes
 
MVP

The dependency that is causing the cycle is a weak dependency (consumption of a few entities in OAuth2_CrossTenant). See the list of weak dependencies in here: https://success.outsystems.com/documentation/11/building_apps/reusing_and_refactoring/understand_strong_and_weak_dependencies/

Therefore, it should not cause an architecture violation. You might want to submit a support case if this is being flagged as a violation.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.