Diggory Mark wrote:
> Now, If someone might invest the time to get us on JSP 2.0 rather than
> this antiquated JSP 1.x version we are using, then we could upgrade
> the JSLT libraries as well and use EL syntax to reference things
> rather than JSP<%=%>  tags. then it would look much cleaner to you.
> JSP has come a long way since these JSP's were written, I can't
> believe the community hasn't pushed to get this more updated, it
> probably make customization of the JSPUI significantly easier and
> allow the use of editors/services/tools that work better with the 2.0
> syntax... I.E. Dreamweaver etc.

Ahh... well. The 1.5 codebase is basically the wrong place to try and do 
it (too much 'wasted' effort).

What I had been hoping / intending to do with DSpace 2.0 is turn 
'dspace-jspui-api' into 'dspace-servlet-api', and rip out the JSPManager 
in favour of a more generic ViewManager.

Then people can build different WAR types off of that with different 
view technologies - JSP 2.0, Velocity, Freemarker, etc. (And probably 
implement a JSP 2.0 based interface, generating very minimal XHTML + CSS).


> Interestingly this is exactly what JSTL/JSP 2.0 meant to alleviate, a
> lot of custom JSP tag-libraries became obsolete with the creation of
> JSTL.

Yes, and custom tags can also be implemented in .tag/.tagx files, that 
are structured like jsp/jpsx, for reusable components that do generate 
XHTML.

G
This email has been scanned by Postini.
For more information please visit http://www.postini.com


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to