[sakai2-tcc] Experimental 1.2 jsf branch

[Aaron Zeckoski]

I should add to this by mentioning that the JSP issues were solved and
I have used JSP + Spring MVC on a few recent projects. It works quite
well. I don't want anyone to get the wrong impression here. JSF is not
needed in order to use JSP in Sakai.

Here is a tool using JSP + Spring MVC.
https://source.sakaiproject.org/svn/msub/unicon.net/kaltura/trunk/

Here is one that only uses JSP.
https://source.sakaiproject.org/contrib/iclicker/trunk/

Hope this helps!
:-)
-AZ


On Wed, Feb 23, 2011 at 10:02 AM, Mark Norton <markjnorton at earthlink.net> 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
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>



-- 
Aaron Zeckoski - Software Engineer - http://tinyurl.com/azprofile