It looks like this flame war isn't going to die out, after all...
"Shad J. Aumann" <[EMAIL PROTECTED]> wrote:
>These comments are not entirely accurate. Some important development team
>synergy issues have been ignored.
For the sake of accuracy, you may want to take a look at the most
recent JSP specification. The tag extension feature introduced in JSP
1.0 and spec'd out in JSP 1.1 directly addresses what appears to be
your primary complaint: you don't want Java source code in the middle
of your HTML files.
Like yours, our team here has a group focused on presentation (HTML),
and a group focused on back-end implementation (Java). We use JSP for
dynamic content, and we don't put Java source code in our .jsp files.
>Having the web-based GUI team members simply place marker tags (we use a
>specially formatted HTML comment) in their GUI templates where the servlet
>should dynamically inline data at runtime (yes, a lot like JSP, but the
>distinction is important) is perfectly reasonable.
Using marker tags doesn't seem very different to me from using custom JSP tags.
>I will not even touch upon the performance issues of JSP versus other forms
>of servlet-based data inlining into an HTML GUI template...
But JSP *is* servlet-based data inlining into an HTML GUI template! I
don't follow you here. And given that the servlet code written by the
JSP pagecompiler is automatically generated, it certainly has the
potential to outperform handwritten code.
- Mark A. Kolb Staff Engineer
[EMAIL PROTECTED] Tivoli Systems Inc.
http://www.cross-site.com (512) 436-1955
___________________________________________________________________________
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
