Inject CrowdService instead of UnfilteredCrowdService for normal usage

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Duplicate
    • Component/s: 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

            Assignee:
            Unassigned
            Reporter:
            Alex Wei (DE)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: