On Tue, May 25, 1999 at 03:23:51AM +0000, Craig R. McClanahan wrote:
> On the other hand, even if they do, a standardized scripting environment
> is still IMHO better than a non-standardized template world that locks
> you in to a particular vendor (even if the source code of the template
> engine is free, the cost of switching later is very high).
This is an argument that makes no sense to me. I've
used three different template systems (one Perl, two Java), and
none of them have ever left me "locked in" to any of them.
I've also switched one program from using MessageFormat
substitution in a (ahem) "novel" way to using templates. The cost
of switching was very low, since the text work only happened
in one place. The servlets I've worked on have had a similar
structure: all of the business logic is completed, ending with
a set of results to show to the user. The last step is building
the data structure to hand off to the template engine.
Yes, the cost of switching for a very large project would
be high. But that cost would be more than offset by the lower
development and maintenance costs, and the likelihood of needing
to switch template engines is very low.
Question for the JSP side: How do you test a JSP to see
if it's functionally correct?
--
Robert Crawford [EMAIL PROTECTED]
http://www.iac.net/~crawford
___________________________________________________________________________
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
