Zacharias,
thanks for your interesting remarks. Am I understanding you right that
JSWDK does not have the restrictions of Tomcat you've described?
I'm not using JSWDK (or Tomcat) in a production environment. It should
rather serve as to what it has been designed for, namely a reference
implementation. So if anything doesn't work as expected with another
servlet engine (I personally like ServletExec), I go to the reference
implementation and try to reproduce the problem case.
Of course, there should be only one reference implementation. For now,
I've decided to stick with JSWDK until the merger with Tomcat has been
officially announced.
BTW, what features does Tomcat have that JSWDK has not?
Heinz Wehner
(Karlsruhe, Germany)
> -----Urspr�ngliche Nachricht-----
> Heinz Wehner wrote:
>
> > Is there any reason why one should keep my JSWDK 1.0.1 installation?
>
> Yes. As of today, the integration between the two is awful. Very hard to
> figure out, and I haven't been able to get tomcat to do what I need...
> Specifically, we want our existing web site to handle JSP pages.
> With tomcat installed, it seems that the only way to do this is move the
> entire web site to the tomcat server--i.e.: you can have JSP, but only
> if tomcat is the server for the entire web site. You can't, as far as I
> have been able to determine, simply have tomcat execute JSPs within an
> existing Apache web site.
>
> Also, we want to execute servlets within the Apache web site. We
> have a mix of html, phtml and JSP code, and now we are adding servlets.
> Again, the servlets seem to require the entire tomcat server setup --
> which means, we might as well turn off Apache. This is not acceptable
> for us...
>
> Now, I suspect that there is a way to make this work, but I've just
> spent an entire long weekend (three days) trying to make tomcat execute
> a JSP within our Apache site, and haven't been able to do it. All I can
> do is set up separate web sites (within the tomcat web server
> directories) and execute them there...
>
> Bottom line is that tomcat still runs as a completely separate server.
> When Apache sees a URL that says "something to do with Java" it hands
> that URL off to tomcat... and tomcat proceeds to search its internal
> web configuration for the relevant pages. Hopefully this will be fixed
> -- judging by what I've seen on the Jakarta site, the long-term plan
> is to merge the functionality of these two products. But for now,
> think of them as separate products that hand things back and forth,
> which (at least for our purposes) often isn't going to get you
> where you need to be...
>
> --
> Zacharias J. Beckman - [EMAIL PROTECTED] - (U.S.) 305-281-8701
> Creative Sun Inc., Publishing for the Internet -
> http://www.creativesun.com
___________________________________________________________________________
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
