[WG: Sakai QA] Sakai QA] Another request for special QA properties
Berg, A.M.
A.M.Berg at uva.nl
Sat Jan 30 01:46:00 PST 2010
Done for qa1-nl.
Alan
Alan Berg
Interim QA Director - The Sakai Foundation
Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam
http://home.uva.nl/a.m.berg
-----Original Message-----
From: sakai-qa-bounces at collab.sakaiproject.org on behalf of Steve Swinsburg
Sent: Sat 1/30/2010 0:47
To: Sakai QA WG (sakai-qa at collab.sakaiproject.org)
Subject: [WG: Sakai QA] Another request for special QA properties
Whilst on the topic of adding properties to the QA servers, could the following please be added as well.
# Set this to tell the ProfileManager to get it's data from Profile2.
# If left unset, any tools that use the ProfileManager from the original profile tool (ie Roster)
# will continue to use the data from org.sakaiproject.api.app.profile.LegacyProfileManager.
# So you must set this to enable the integrations.
# If you are using a version of Sakai prior to 2.7, you need to apply the patch attached to http://jira.sakaiproject.org/browse/SAK-17573
# in order for this property to have any effect
profile.manager.integration.bean=org.sakaiproject.profile2.legacy.ProfileManager
By default, the classic ProfileManager will continue to use org.sakaiproject.api.app.profile.LegacyProfileManager as its source of data. Since the Roster looks to the profileManager, this means that you won't see the Profile2-Roster integration. Adding the property above as-is will enable this.
regards,
Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20100130/b3f6b8b8/attachment-0001.html
More information about the sakai-qa
mailing list