OK. Sorry if I've confused things, but to an end-user like me, with the
requirement "JSP on Apache", it's not clear where Tomcat stops and
something else starts (although as a software engineer I understand why the
design is so modular).
Andrew
At 12:17 PM 8/3/01 +0100, you wrote:
>Andrew Cooke at [EMAIL PROTECTED] wrote:
>
> > At 12:43 PM 8/3/01 +0200, you wrote:
> >>> - Tomcat 4.0b6 does not work with Apache out of the box
> >>
> >> That is why (among other things) it is beta.
> >
> > I realise it's beta. However, in an earlier thread ("SAX 2.0, sealing,
> > Tomcat 3.2.3") several people (IIRC) suggested that it was solid and usable
> > (and only beta because it was tracking changing APIs).
>
>That's correct... Tomcat 4.0B6 is way stable. I'm using it myself in
>production on a Sun E4500 running Solaris 8, and so far it hasn't given a
>single problem. It just runs smooth as a charm.
>
>The WebApp Module for Tomcat 4.0 though, _IS_ beta (not even, I call it
>alpha), that's why it is _not_ distributed with TC4, but there's only a
>refence to it in its server.xml configuration file.
>
>Tomcat 4.0 is stable, it's add-ons (especially this one, since I wrote it)
>are not... :)
>
> Pier
