Heinz Wehner wrote:
> Craig,
>
> my conclusion is to think of:
>
> - JSWDK as the reference implementation for Servlet 2.1/JSP 1.0
> - Tomcat as the reference implementation for Servlet 2.2/JSP 1.1
> (and future APIs)
>
> I'm currently participating in a project where JServ 1.0 is to be used
> as the servlet engine. Now JServ 1.0 implements the Servlet 2.0 API.
> So what is considered to be the reference implementation for this API?
> It could make sense to get and install it just in case it is required
> to compare how JServ 1.0 and the reference implement a feature.
>
JSDK 2.0 is the reference implementation for the 2.0 API. You should be aware,
though, of a couple issues:
* There are Y2K problems in the servlet API classes -- I believe there's a
patch out.
* The servlet runner included in JSDK 2.0 serves only servlets, not files.
You might have to take that into account in the places where you are
letting Apache serve the static content parts of your app.
One other suggestion -- at all costs, avoid the 2.0 methods that are deprecated
in later APIs (getServlet(), HttpSessionContext related stuff, and so on).
Otherwise you are going to face a rewrite when you eventually move forwards to
a servlet engine based on a later API.
>
> Heinz Wehner
> (Karlsruhe, Germany)
>
Craig
___________________________________________________________________________
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
