Earl,
If you think one should not discuss the merits of JSP here, you should
not take part on it even if to defend JSP.
If you agree we should talk about the pros and cons of JSPs, it is hard
to talk about the cons of JSP in a constructive way without pointing
alternatives. Can one just say it is bad without pointing alternatives
and still give worthy input?
Or do you just want to talk about the pros?
=;o)
Clearly, there are some problems with JSPs. Supporting a clear
separation between logic (scripting) and presentation (templating) is
not easy to enforce with JSPs. And this is a discussion going on in
many forums.
Now, JSPs are nice for scripting stuff (when you want to code and see
the result with no compiling/restarts). I even thought of using JSPs
for the scripting with Velocity for templating!!! And this is not such
new idea since there are people using JSPs with XSLT for the same
purposes.
But XSLT just makes things too hard. Too much cost for not enough
profit. I just converted a XSLT based application to Velocity and I
sure know what I am talking about.
Maybe JSPs just need something extra for the templating side. Maybe
JSPs can learn that from Velocity/WebMacro template engines.
And this list is one of the best spots to talk about this. The right
people read this. * Isn't Tomcat the reference JSP implementation? *
Have fun,
Paulo Gaspar
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 06, 2001 18:48
>
> Why has the tomcat-dev list become a Velocity advocacy list??
> Isn't the purpose of this list supposed to be for communation between
> Tomcat developers? Is velocity recruiting or something?
>
> =eas=
