[sakai2-tcc] [Building Sakai] Experimental 1.2 jsf branch

[David Horwitz]

A note on this a bit of research - JSF 1.2 requires jsp-api 2.1 and
servlet-api 2.5. So jsf 1.2 won't run on tomcat 5.5. If we want this we
need to upgrade to tomcat 6

See for instance:
http://www.roseindia.net/jsf/jsf1.2/jsf1.2features.shtml

D

On 02/24/2011 12:36 AM, Anthony Whyte wrote:
> Here is a list of all projects with one of more jsf dependencies with
> the following groupId: <groupId>org.sakaiproject.jsf</groupId>.  Past
> decisions weigh heavily on us in this case.
>
> Active
>
> jobscheduler
> msgcntr
> osp
> samigo
> sections
> site-manage
>
> Maintenance
>
> calendar summary tool
> chat
> gradebook
> help
> jsf  
> metaobj
> podcasts
> postem
> profile (ye old version, deprecated)
> roster
> syllabus
> tool
> user
> usermembership
> was (websphere project)
>
> Cheers,
>
> Anth
>
>
>
> On Feb 23, 2011, at 5:14 PM, Steve Swinsburg wrote:
>
>> Is Samigo the only project that uses JSF and is under active
>> development by a project team? If so, it seems prudent that they are
>> given the freedom to manage their own JSF version upgrades. IMO, once
>> this initial work on upgrading JSF for the current tools that are
>> supported by the Maintenance Team is done (chat, roster, et al), we
>> should cut our losses and not tie up any more developer resources
>> with it.
>>
>> There is no (supported) Sakai Wicket bundle, and for good reason:
>> using Vanilla Wicket is far superior and gives a project team the
>> freedom to upgrade versions of Wicket whenever they like. Can the
>> same be said for JSF? If so, perfect, let each project manage it's
>> own JSF version.
>>
>> cheers,
>> Steve
>>
>>
>> On 24/02/2011, at 2:37 AM, Mark Norton wrote:
>>
>>> 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
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> <mailto: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"
>>
>>
>
>
> _______________________________________________
> 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/20110224/5b736d62/attachment-0001.html