RE: You make the decision Velocity/Turbine vs. Struts/JSP

[di...@multitask.com.au]

Or to put it another way, 

Putting Velocity on top of Servlets doesn't fix the warts in Servlets. It 
simply hides them until your developers  find them.

See getInitParameter in ymtd.
--
dIon Gillard, Multitask Consulting
Work:      http://www.multitask.com.au
NetRexx: http://www.multitask.com.au/NetRexx.nsf
----- Forwarded by dIon Gillard/Multitask Consulting/AU on 09/03/2001 
01:32 AM -----
RE: You make the decision Velocity/Turbine vs. Struts/JSP

>
> But, the point of what I am trying to say (and I will try to
> clarify it
> further in the document) is that by using Struts and JSP there is *NO*
> enforcement that requires you to not use scriptlets.
>
[snip]
> Putting Struts on top of JSP doesn't fix the warts in JSP. It
> simply hides
> them until your developers find them.
>
Jon; if I read you correctly a JSP engine would be better for having its
scriptlets capability disabled. Or less radically allow the it to be
specified in the web.xml file that scriptlets are not allowed for a given
web-app. I think I buy that. In retrospect I even wish I had been able to 
do
that on a few JSP projects past.

Joerg Beekmann
jbeekmann@attglobal.net





Previous Document


Next Document
Return to View