IMHO it depends how your application is developed.
If you as a are writing what is a essentially a Java program that needs
to be presented by an HTML user interface then the template solution seems
much better.
However, if you are building what is essentially an HTML web-site, which
needs to generate some stuff dynamically then a JSP approach is better.
It depends on your perspective which is a better solution and hence
neither is really better, they just suit different types of applications
and different types of teams.
In terms of standards support neither is really better because both are
built on the Servlet API (barring the fixing up that the API needed
to make JSP work) which already provides the run anyway property.
I would even suggest that you could use both types of solution within a
single Web-site!!!
Tom
On Wed, 26 Jan 2000, Govind Seshadri wrote:
> Interesting article...although I mostly disagree with the notion that
> using WebMacro is a 'great leap forward' compared to using JSPs and
> custom taglibs.
>
> Anyway, what is so special about WebMacro in particular? Why not use
> Cocoon, Turbine, Freemarker, OTembo or even ECS? They all offer similar
> features and I daresay, some of them are probably better supported than
> WebMacro.
>
> cheers,
> Govind Seshadri
>
> Jason Hunter wrote:
> >
> > Hello everyone,
> >
> > I just posted a new article to Servlets.com titled "The Problems
> > with JSP" that will be of particular interest to the people on
> > this list. From the first paragraph:
> >
> > By now almost everyone using servlets has heard about JavaServer
> > Pages (JSP), a Sun-invented technology built on top of servlets.
> > Sun has done a marvelous job promoting JSP as a way to get HTML out
> > of servlet code, speeding web application development and improving
> > web page maintenance. In fact, the official "Application Programming
> > Model" document published by Sun has gone so far as to say, "JSP
> > technology should be viewed as the norm while the use of servlets
> > will most likely be the exception." (Section 1.9, December 15, 1999,
> > Draft Release) This paper evaluates whether that claim is valid --
> > by comparing JSP to another technology built on servlets:
> > template engines.
> >
> > The article is available at:
> >
> > http://www.servlets.com/soapbox/problems-jsp.html
> >
> > -jh-
> >
> > --
> > Jason Hunter
> > [EMAIL PROTECTED]
> > Book: http://www.servlets.com/book
> > 2.0 to 2.1: http://www.javaworld.com/jw-12-1998/jw-12-servletapi.html
> > 2.1 to 2.2: http://www.javaworld.com/jw-10-1999/jw-10-servletapi.html
> >
> > ===========================================================================
> > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
> > FAQs on JSP can be found at:
> > http://java.sun.com/products/jsp/faq.html
> > http://www.esperanto.org.nz/jsp/jspfaq.html
>
> --
> Govind Seshadri <[EMAIL PROTECTED]>
> jGuru.com - Your Gateway to the Java Universe
> http://www.jguru.com
>
> ===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
> FAQs on JSP can be found at:
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
