Another approach to applying Java Servlet technology is to use a Java
Beans framework with template pages. This may have fewer layers of
learning curve to climb than the JSP approach with custom tag libraries
(and all that stuff). And it provides the separation of programmer
process from page designer process (which in the real world is not
always easy with JSP) if the logic is on the Servlet side and the
template language does not intrude with too much whiz-bang programmer
syntax on the web page. One possibility in that space is JOT Servlets (a
product I'm involved with).
http://www.jotobjects.com
-- Paul Copeland, JOT Object Technologies
> Date: Wed, 18 Apr 2001 12:42:09 -0700
> From: Alex Amies <[EMAIL PROTECTED]>
> Subject: Re: Servlet versus JSP
>
> Working with designers with xml/xsl is a similar story as with
> jsp: a programmer really has to do the work. What we have
> done here is that a designer came up with photoshop drawings /
> static html for about 4 screens. We took that and produced style
> sheets so that our 130+ screens all come out to look the same.
>
> That is better than jsp. What usually happens there is that the
> html done by a designer has to refined by a programmer so that it
> is more suitable for dynamically generated data /
> internationalization. Then you end up using cut and paste to
> copy thousands of lines of html into jsp's.
___________________________________________________________________________
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
