[Building Sakai] 2.7.0: Profile2 v Profile

[Adrian Fish]

I know I have a vested interest in Profile2's being adopted 
wholeheartedly but I can't see any reason why people would want to run 
the old profile tool and not move, apart from incompatibility with 
current tools. If current tools CAN work with profile2 without code 
changes than I can conceive of no argument whatsoever for keeping the 
old tool. Profile2 is light years ahead of the old tool in UI and levels 
the playing field with competing platforms regarding profile management.

+1 to removing the old tool and replacing it with Profile2

Cheers,

Adrian.

Anthony Whyte wrote:
> I assumed that profile would be replaced by profile2 if the latter got 
> the nod for 2.7.0 (it has) but I'd like others to consider the 
> implications of what Steve writes below and comment on list.
>
> Cheers,
>
> Anth
>
> Begin forwarded message:
>
>> *From: *Steve Swinsburg <steve.swinsburg at gmail.com 
>> <mailto:steve.swinsburg at gmail.com>>
>> *Date: *December 11, 2009 6:36:05 PM GMT-05:00
>> *To: *Anthony Whyte <arwhyte at umich.edu <mailto:arwhyte at umich.edu>>, 
>> Clay Fenlason <clay.fenlason at et.gatech.edu 
>> <mailto:clay.fenlason at et.gatech.edu>>
>> *Subject: **Re: Profile2 v Profile*
>>
>> Actually, if this is an issue I could do it a different way. I might 
>> be able to create a separate implementation of the ProfileManager API 
>> and bundle that with Profile2 instead, leaving the current 
>> ProfileManager API untouched. You could then just swap the beans out 
>> in the Roster config to activate it. This would mean touching code to 
>> activate Profile2 though and I don't know if you just want to remove 
>> the Profile altogether.
>>
>> I didn't want to do this initially as it meant touching a few more 
>> tools but if it's necessary I guess I'll need to do it.
>>
>> Let me know how you want to proceed.
>>
>> cheers,
>> Steve
>>
>>
>> On 12/12/2009, at 10:26 AM, Steve Swinsburg wrote:
>>
>>> Hi Anthony and Clay,
>>>
>>> Just a heads up, which I am not sure the PC are aware of as such, is 
>>> that the Roster integration work with Profile2 essentially renders 
>>> the existing Profile unusable, so when it goes into trunk, the 
>>> Profile will need to be removed.
>>>
>>> I had to re-write the legacy ProfileManager to get its data and 
>>> privacy settings from Profile2 rather than Profile so the Roster 
>>> will get the right info. This then deploys itself as the same 
>>> artifact so it overwrites the one produced from the Profile tool. 
>>> This is the only way to do it otherwise there would be two 
>>> implementations of the ProfileManager API.
>>>
>>> I hope this doesn't upset the apple-cart but it was a necessary move 
>>> to get the integration working.
>>>
>>> Let me know if you need any more info.
>>>
>>> thanks,
>>> Steve
>>>
>>>
>>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-- 
==================================
Adrian Fish
Software Engineer
Centre for e-Science
Bowland Tower South C Floor
Lancaster University
Lancaster
LA1 4YW
email: a.fish at lancaster.ac.uk

http://confluence.sakaiproject.org/display/YAFT/Yaft
http://confluence.sakaiproject.org/display/BLOG/Home
http://confluence.sakaiproject.org/display/AGORA/Home

-------------- next part --------------
A non-text attachment was scrubbed...
Name: a_fish.vcf
Type: text/x-vcard
Size: 289 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20091214/687dfaa5/attachment.vcf