[sakai2-tcc] JSF Upgrade for Sakai 2.9?

[David Horwitz]

There may be a way forward (and it may be facilitated by the fact that
the tools can define their own version of jsf).

We branch the jsf project. So we have at the outset 2 releases aimed at
the 2.9 release:

1) 2.9.0-jsf111 - binds to the current 1.1_01 jsf and is by implication
deprecated (i.e. there will be no new release of this for 2.10 if no
core projects need this by the 2.9 release it won't be released)
2) 2.9.0-jsf112 - binds to jsf 1.1_02 many tools can switch straight to
this, others that need some tweeks (like msgcntr) can do so as and when
the project teams can get the resources together.

If we can get the resources and expertise to upgrade the JSF project to
the latest 1.2 release (1.2_15) Then branch 2 above also gets marked as
deprecated with a reasonable timeframe to migrate to the new branch.

Thoughts?

D


On 02/18/2011 10:53 PM, Maurer, Christopher Wayne wrote:
> (Comment from a lurker who is not a member of the TCC)
>
> We at IU see some nodes in our app server cluster fall victim to the
> "death by jsf" issue from time to time.  We'd definitely be in favor
> of whatever upgrade can correct it!  I'm not the one to officially
> volunteer resources to help with the effort, but I'm sure Megan could
> be convinced that someone at IU could/should get involved in some way!
>
> Chris
>
> From: David Horwitz <david.horwitz at uct.ac.za
> <mailto:david.horwitz at uct.ac.za>>
> Date: Fri, 18 Feb 2011 22:48:19 +0200
> To: <sakai2-tcc at collab.sakaiproject.org
> <mailto:sakai2-tcc at collab.sakaiproject.org>>
> Subject: Re: [sakai2-tcc] JSF Upgrade for Sakai 2.9?
>
> I had a brief look at this and found it difficult and simply I did not
> have the JSF knowledge to do this. I'll update the jira but I think
> the postem one was not a library incompatibility but a packaging
> problem. The remaining problem was that certain JSF tools  (msgcntr &
> sam?)displayed the alert messages box all the time even if there was
> no alert. Note this was simply to the next 1.1 release nothing like an
> upgrade to 1.2 or even JSF 2
>
> Seeing we have regular app server deaths (well stuck threads at high
> load that force us to restart) regularly due to JSF bugs I think this
> is something we have to look at. Quite frankly to solution might be to
> get rid of JSF (though thats unlikly to happen)
>
> D  
>
> On 02/18/2011 10:17 PM, Matthew Jones wrote:
>> My guess is that even because minor upgrades of JSF require major
>> code changes across the most of the codebase?
>>
>> https://jira.sakaiproject.org/browse/SAK-19282 (Attempt to
>> upgrade 1.1.01 to 1.1_02 completely broke postem)
>>
>> Typically Dave Horwitz has been the one looking at these library
>> upgrades, but the large amount of cross cutting maintenance work,
>> combined with testing just has never been there to make the gains
>> from upgrade worth it. I'd guess this is well over a 100 hours project.
>>
>> It took almost 5 years to get around to upgrading James and it's only
>> used by email archive. ;)
>>
>> -Matthew
>>
>> On Fri, Feb 18, 2011 at 2:56 PM, Beth Kirschner <bkirschn at umich.edu
>> <mailto:bkirschn at umich.edu>> wrote:
>> >
>> > Does anyone know of a reason _not_ to upgrade JSF to version 1.2?
>> It's causing problems with several tools, as noted in
>> https://jira.sakaiproject.org/browse/SAK-20086
>> >
>> > - Beth
>> > _______________________________________________
>> > sakai2-tcc mailing list
>> > sakai2-tcc at collab.sakaiproject.org
>> <mailto:sakai2-tcc at collab.sakaiproject.org>
>> > http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>
>>
>> On Fri, Feb 18, 2011 at 2:56 PM, Beth Kirschner <bkirschn at umich.edu
>> <mailto:bkirschn at umich.edu>> wrote:
>>
>>     Does anyone know of a reason _not_ to upgrade JSF to version 1.2?
>>     It's causing problems with several tools, as noted in
>>     https://jira.sakaiproject.org/browse/SAK-20086
>>
>>     - Beth
>>     _______________________________________________
>>     sakai2-tcc mailing list
>>     sakai2-tcc at collab.sakaiproject.org
>>     <mailto:sakai2-tcc at collab.sakaiproject.org>
>>     http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>
>>
>>
>> _______________________________________________
>> sakai2-tcc mailing list
>> sakai2-tcc at collab.sakaiproject.orghttp://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>   
>
> _______________________________________________ sakai2-tcc mailing
> list sakai2-tcc at collab.sakaiproject.org
> <mailto:sakai2-tcc at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20110219/7a929474/attachment.html