[sakai2-tcc] Experimental 1.2 jsf branch

[Mark Norton]

Sadly, I have little time to spend on dying UI technologies.  Though I 
was proficient with JSF at one time (years ago), I've given up on it.  
RSF was far better, though support for it is questionable these days.  
Most of my work outside of Sakai uses JSP, using a development 
methodology that avoids some of its problems (cryptic jsp files).

Regarding JSF, I'd be in favor of eliminating it from Sakai but 
migrating Samigo to something else would be far more work than anyone 
would want to contemplate.  I think they can best advise us on forward 
migration of JSF.

- Mark

On 2/23/2011 10:09 AM, David Horwitz wrote:
>> On 2/23/2011 9:27 AM, David Horwitz wrote:
>>> 1) JSF 1.2 requires jsp-api 2.1 - this is deployed to common/lib
>> Although JSF is rather painful to work with, it does provide an
>> interesting feature that I have taken advantage of.  JSF supports JSP
>> rendering and control.  Although I'm sure it was intended as a legacy
>> support feature, it does enable JSP's to work in Sakai.  Aaron Z and I
>> played around with getting JSP to work in Sakai several years back,
>> with limited results.  The problem is buried in the Sakai
>> RequestFilter somewhere.  Regardless, JSF allows a developer to use
>> JSP.  Another reason to keep JSF in Sakai and make sure that we track
>> JSF release the best we can.
>>
>> - Mark Norton
> Perhaps then you might be better placed than me to comment on the likely
> implications viz. existing tools if we upgrade to 2.1 (or even 2.1.2)?
>
> D
>
>