Jason definitely stirred the pot.  To me "The Problem with JSP" is that it
is being discussed way to much in a forum for servlets.

Put since I have been reading the 73 mails thus far on this topic, I feel
obligated to put my 2 cents in.  The one thing the JSP does bring is a
standard mechanism to separate business logic from presentation logic.  It
is all in Java and all part of the standard J2EE spec.

My big problem with template toolkits are they really target one problem
space.  The one where I have some data in a database that I want to publish
in HTML or XML format.  These work great for this and I don't discount there
usefulness.  (Although I would never touch one I could not get the source
for since I have been burned like that in the past.)

There are a another class of web applications out there, where the business
logic is much more complex then a SQL statement.  These require a design
where the business objects live in well formulated objects, in many cases
distributed via EJB, RMI or CORBA.  For these cases, JSP offers a solution
for dealing with presentation aspects.  While it is not completely elegant
at this point, we will get around it's short comings by building custom tag
libraries.

In the end the great thing is I will not be tied to any vendor or platform
and I will be using Java standards.  This is hard to beat.

Frank


***********************************************************************
Bear Stearns is not responsible for any recommendation, solicitation,
offer or agreement or any information about any transaction, customer
account or account activity contained in this communication.
***********************************************************************

===========================================================================
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

Reply via email to