Ted Neward wrote:
> I thought the idea *was* to integrate them somehow.
>
Integration of the Tomcat servlet engine (from JSWDK) and Apache is going to
happen within the auspices of the Jakarta project (http://jakarta.apache.org)
once the source code is released. There will be an Apache module that connects
to the servlet container, similar in concept to the way that Apache JServ
connects today, so that separate port numbers will not be needed (from the end
user's perspective). The JSWDK stuff will also continue to run stand-alone as
it currently does, so you won't have to install a web server for development,
or to deploy apps that do not need the web server features.
>
> <SPECULATION>
> Ted, what if you call the JWSDK classes from within the JServ (or some other
> JVM) engine? That at least saves you the extra round trip through the
> network layer again.
> </SPECULATION>
>
The JSWDK servlet related classes won't completely work, because Apache JServ
1.0 supports the 2.0 API only. This means that new 2.1 features like
RequestDispatcher, request attributes, and context attributes cannot be used.
For the JSWDK JSP engine, that means you cannot use beans with
scope="application" or scope="request", and you cannot use <jsp:include> or
<jsp:forward>. Some other JSP engines try to work around these issues with
custom extensions.
>
> Ted Neward
Craig McClanahan
___________________________________________________________________________
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
