Justin Wells wrote:

> [snip]
> Most of the template solutions allow you a much cleaner separation of
> concerns than is possible in JSP.
>

Among the many threads of conversation you will find in the archives on this topic, 
you will find that I disagree with Justin on this point :-).

JSP, because it includes custom tags, can easily *support* the same separation of 
concerns that template environments like WebMacro and Velocity provide.  The 
philosophical difference that Justin and others articulate is whether the developer 
should be *restricted* to only that approach.  This is an entirely different
kettle of fish.

> [snip]
> WebMacro in particular expects you to develop all of your program
> logic in back end JavaBeans, independent of the fact that you may
> use them in a servlet. It uses bean-like introspection to pull
> properties out of those beans and drop them into the template view.
>

See, for example, Struts (<http://jakarta.apache.org/struts>) for a JSP-based 
framework that has analogous (but not identical) approach.

> [snip]
> As for whether it will disappear--I doubt it, it's an opensource
> project with a large following. Even if the entire development team
> dropped off the face of the planet the community would continue to
> support it.
>

The only point I would add here is that JSP provides you choices of implementation of 
the specification, not just in the functionality provided by the language.  For 
example, if you think that Tomcat's JSP engine is too slow, go use a servlet container 
that is faster without having to give up the language in which you
wrote your pages in the first place.

>
> Justin Wells
>

Craig McClanahan

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to