----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
> > In the future I can imagine them branching, but
> >at this time is it pretty safe to say that the JServ portion used in
> >Tomcat is similar enough in order to have Apache do ApJServMount
> >directives for both JServ and Tomcat?
>
> I haven't tried that approach so again I couldn't say I run Tomcat as a
> standalone. To be honest I am not so impressed with Tomcat so far.. it
> seems to be me unstable to exceptions and JServ visibly out performs
> Tomcat. The only reason I see right now for running Tomcat is for servlets
> requiring JSDK > 2.0 or if you want a more complete JSP platform than the
> cobbled GNU + JServ mish-mash.
Cobbled is a good adjective. I do appreciate the effort of the GNU JSP
group, but getting beans to reload (or be found) with JSP is voodoo. My
impetus for running Tomcat concurrently is to offer JSDK 2.2 for some
virtual hosts with the anticipation of eventually using Tomcat as the
primary engine. Part of the transition is also a need to move toward
private JVMs for added security and privacy, so the exceptions & whatnot
aren't much of a problem for me as long as one user only brings down
their own instance.
> >I'm currently trying to implement Tomcat alongside of JServ. So far I
> >have found some peculiar issues with the URL (where the URI says
> >/servlet/servlet), but other than this it seems to work fine for me.
>
> Tomcat is harder to configure in my opinion... unnessarily so, which is
> surprising given how many people have trouble getting JServ up and
> running. Clearly it has a way to go till many of us would consider it a
> viable option apart from the reasons above. I 'd be interested in knowing
> why Oracle chose JServ over Tomcat given that JServ only supports the
> older JSDK.. .. oh to be a fly on the wall. Have you red the article on
> the java.apache.org home page?
Interesting article. Most likely they chose JServ in order to have SSL
capability, but I would expect them to go with Tomcat down the road. I
also find Tomcat hard to configure, but in retrospect JServ seemed very
complex the first time around. Probably my biggest gripe with Tomcat
configuration is the apparent lack of option to define the location of
your servlets directory. For my migration purposes it will be somewhat
confusing to users to reference
$TOMCAT_HOME/webapps/<context>/WEB-INF/classes.
If anyone else out there has a success story of using JServ and Tomcat
together I would be interested to hear about, along with any hurdles you
found in the process.
Duane
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
