Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-17573

Convert ProfileManager into a proxy bean that can load any given implementation and let the Profile tool use the legacy bean by default

    XMLWordPrintable

    Details

    • Type: Task
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.7.0
    • Fix Version/s: 2.7.0
    • Labels:
      None

      Description

      ProfileManager will be converted into a proxy bean that gets the actual bean id to use as the implementation from sakai.properties like so:

      profile.manager.integration.bean=org.sakaiproject.api.app.profile.LegacyProfileManager

      The value above is the default. Thus, the actual implementation of ProfileManager has been converted into LegacyProfileManager. The profile tool uses this legacy bean and is unaffected.

      This allows different implementations to be plugged in via sakai.properties, eg a Profile2 impl of the ProfileManagerso that Roster and other tools can get their data from Profile2 preferentially, if desired, and without affecting any other tools.

      This will also allow both Profile and Profile2 to run side by side

        Gliffy Diagrams

          Zeplin

            Attachments

              Activity

                People

                Assignee:
                steve.swinsburg Steve Swinsburg
                Reporter:
                steve.swinsburg Steve Swinsburg
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Git Integration