On Wed, 9 Feb 2000, Simon Holm wrote:
>> I planning to use JSP ...
[snip]
>> ... Then I find this negative argument in this article:
>>
>> http://www.servlets.com/soapbox/problems-jsp.html
Simon,
1) I think you need to read the article for what it is, an opinion.
There are some good points in there, but a lot of it is based
on personal styles and one particular mechanism isn't necessarily
going to work best for everyone.
2) If you are coming from an ASP background, you will probably be
much more comfortable with the style of development in JSP better
than the template engines mentioned in the article.
3) JSP gives you the ability to add functionality as you need it.
Template engines often require you to rely on upgrades to the
software to add new functionality. Sometimes, they may actually
allow bridges to other development environments to add custom
functionality, but you can't necessarily count on it.
4) Platform/server independence is most likely going to be in the
favor of JSP (remembering that it is relatively in its infancy
and only getting better) as opposed to template engines that
are either compiled for a particular OS/server - or rely on
other technologies (like java/perl) to do their processing.
--
Much of what the article mentioned about separating business logic
being 'cleaner' in the template engines is true. This comes at the
expense of being locked into the functions provided by the engine.
What it will come down to is taking a look at the skills of the
people involved, the outcomes you are trying to achieve, and
deciding which particular methodology works best in that environment.
- vin
===========================================================================
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
