I am trying not to follow-up on things that have been drilled to death.
That does not mean I agree with everything that has been said but I am
sure most of you are dead tired of this thread.
Here are twp that I have not seen addressed:
Jason writes...
> > Tools like this makes it possible for people
> > without programming skills to develop fairly sophisticated dynamic
> > web sites.
>
> If a tool can generate a JSP page, why can't the tool just directly
> generate a servlet? :-)
Two answers:
A JSP page is a standard description of action/presentation. That means
you can take your JSP page and move it from one authoring tool to
another authoring tool and the tool will understand what the JSP page is
about and will be able to do inteligent things with it. It also means
the tool can use any custom tag library. It also means somebody can
author a tag library and have it run with any tool.
Although the translation between a JSP page and a Servlet can be done
off-line and expressed as a Servlet using the standard SPIs in the
Servlet & JSP specifications, the JSP can also be delivered as such to
the JSP container. In that case, the JSP container can do a translation
that takes advantage of private SPIs.
Jason says later...
> > The standard tag library will likely make this point moot.
>
> Maybe. The taglib will be designed by committee. Watch out!
The tag library will be designed using the JCP process. That is the
same way we have designed most of the Java platform (including, from
direct experience, JavaBeans 1.0, Servlet 2.2, JSP 1.0 & 1.1, and
JavaHelp 1.0), and the way all of the Java platform will be designed.
Hope this helps,
- eduard/o
===========================================================================
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
