-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Currently, if a component or action requires filtered CrowdService, Spring will throw an exception because it finds two beans implementing that interface. So we have a workaround to inject the UnfilteredCrowdService instead, but that defeats the purpose of filtered CrowdService.
Workaround has been applied to two classes:
- LegacyStudioImportManager
- StudioEditProfile
- is duplicated by
-
CLOUD-4290 Use @Qualifier("crowdService") to select filtered CrowdService where hidden groups are not used.
- Closed