[Building Sakai] Sakai Presentation layer

[markjnorton at earthlink.net]

One of the things I do in my JSP-based applications is to create framework-like support features.  These include things like standard layout templates, access to the current user, permission/role checks, etc.  I have my own flavor of java.util.Writer that converts single quotes to double quotes, which makes code a lot more readable when generating HTML from code.

- Mark Norton

-----Original Message-----
>From: Hedrick Charles <hedrick at rutgers.edu>
>Sent: Feb 23, 2014 3:30 PM
>To: Cris J Holdorph <holdorph at unicon.net>
>Cc: sakai dev <sakai-dev at collab.sakaiproject.org>
>Subject: Re: [Building Sakai] Sakai Presentation layer
>
>The advantage of pure JSP is that you can do anything you need to do. I found in JSF I’m too often fighting the framework. With RSF that is rare. The big problem I have is that it’s really not being supported anymore. Documentation is sketchy. If I were doing Lessons again I’d probably do it with JSP, though it’s pretty clear that I would have had to do more work that way.
>
>On Feb 11, 2014, at 5:10:01 PM, Cris J Holdorph <holdorph at unicon.net> wrote:
>
>> I develop all my Sakai tools using Spring MVC and JSP as the templating 
>> layer.  These tools are client specific and do not exist in the generic 
>> Sakai codebase.  However, there is a tool developed by other Unicon 
>> employees including Aaron Zeckoski and Bob Long based on Kaltura 
>> integration that is an example Spring MVC/JSP tool.
>> 
>> I can not compare the experience of Spring MVC to Wicket.  I know I 
>> absolutely hated JSF and RSF.  Wicket felt like yet another component 
>> technology even if it was better, the component technology was part of 
>> what I didn't like about JSF and RSF, so I did not ever pursue trying to 
>> create a tool using it.
>> 
>> While there may not be any tools listed on that page, there are 
>> definitely a lot of Sakai tools written in JSF.  It's not a technology I 
>> would recommend, but rest assured it's in heavy use.
>> 
>> ---- Cris J H
>> 
>> On 02/11/2014 03:01 PM, Jaco Gillman wrote:
>>> Hi all
>>> 
>>> After many hours of struggling to make a new Sakai tool work like I
>>> expected inside the Sakai framework, I went back to the Sakai
>>> documentation and came across the different Presentation Layers
>>> (https://confluence.sakaiproject.org/display/BOOT/Presentation+Layer)
>>> 
>>> Java Server Pages (JSP)
>>> 
>>>  - no documentaion, and no current Sakai tools listed here
>>> 
>>> Java Server Faces (JSF)
>>> 
>>>  - documentaion found, but no current Sakai tools listed here
>>> 
>>> Reasonable Server Faces (RSF)
>>> 
>>>  - documentaion found, Sakai tools listed here
>>> 
>>> Apache Wicket (Wicket)
>>> 
>>>  - documentaion found, Sakai tools listed here
>>> 
>>> I then found a page where these technologies are compared:
>>> https://confluence.sakaiproject.org/display/BOOT/Comparing+Sakai+Display+Technologies
>>> 
>>> *_The following stood out from the list:_*
>>> 
>>> *JSP - /No real integration with Sakai other than the fact that it is
>>> functional/*
>>> 
>>> 
>>>        JSF - Integration with Sakai - /Has widgets and best integration
>>>        with Sakai (currently) that is being kept up to date/
>>> 
>>> 
>>>        RSF - Integration with Sakai - /Current average but improving
>>>        rapidly, new widgets being developed/
>>> 
>>> 
>>>        Wicket - Integration with Sakai - /Excellent, see the existing
>>>        tools for the minimal setup required/
>>> 
>>> Wicket and JSF seems to be the better options.  How relevant are these
>>> today? Is there still no real *JSP* integration with *Sakai*? I guess my
>>> question is, for someone that has little to no experience on all except
>>> JSP, which Presentation layer option would be a better choice for
>>> creating new tools in Sakai?
>>> 
>>> 
>>> Regards,
>>> 
>>> *Jaco Gillman***
>>> 
>>> Java Developer
>>> 
>>> opencollab
>>> 
>>> *Tel*: +27 21 970 4017  | *Fax*:**+27 21 914 3098**
>>> 
>>> *Email*: jaco at opencollab.co.za <mailto:jaco at opencollab.co.za>  |
>>> *Skype*: gillmanjc
>>> 
>>> *Web*: www.opencollab.co.za <http://www.opencollab.co.za/>
>>> 
>>> 
>>> ------------------------------------------------------------------------
>>> See OpenCollab email disclaimer at
>>> http://www.opencollab.co.za/email-disclaimer
>>> <http://www.opencollab.co.za/email-disclaimer>
>>> 
>>> 
>>> _______________________________________________
>>> 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"
>>> 
>> _______________________________________________
>> 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"
>
>_______________________________________________
>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"