Costin,
I would strongly vote for turning the auto-config back on by default for the
following reasons (other than the fact that I explicity turned it back on
when Keith fixed the ApacheConfig class):
1) This is how 3.2 worked, and how the docs specify that 3.3 works.
2) Configuration of mod_jk is notoriously complicated. Giving people the
auto generated file is a big, big win.
3) For the people who run it in standalone, we can provide a comment in the
file telling them to "comment out the below". That way it would work out
of the box for both types (standalone + behind Apache), and be very easy for
people to tune to their needs.
Since the syntax has changed (and I've never been a server.xml master), I'm
not sure where the AutoConfig stuff would go now.
-Dan
[EMAIL PROTECTED] wrote:
>
> > However, after upgrading to the latest and greatest
> > tomcat 3.3 version out of CVS (as of last night) I've
> > suddenly noticed that tomcat is no longer generating
> > the mod_jk.conf-auto or tomcat-apache.conf files
> > automatically.
> >
> > As near as I can tell, ApacheConfig.execute() is not
> > being called.
>
> Yes, you need to insert the ApacheConfig module in
> server.xml. We can include it by default for
> the next milestone - but I would rather not,
> many people use tomcat standalone.
>
> ( a better solution be part of the new admin interface,
> but probably after 3.3 )
>
> Costin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
--
Dan Milstein // [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
