On Sat, 3 Mar 2001 [EMAIL PROTECTED] wrote:
| 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):
|
| You don't need a "strong" vote -
The attached PATCH modifies
org.apache.tomcat.modules.config.ApacheConfig to add
some needed flexibility. I need someone who is
running apache and tomcat3.3 using mod_jserv to test
it in that
configuration and give their feedback.
I've tested it with mod_jk on winNT and linux 6.2 and
it seems
{sorry about the resend - I hit the send button early
last time}
The attached PATCH modifies
org.apache.tomcat.modules.config.ApacheConfig to add
some needed flexibility. I need someone who is
running apache and tomcat3.3 using mod_jserv to test
it in that
configuration and give their
: Mel Martinez [mailto:[EMAIL PROTECTED]]
Enviado el: lunes 5 de marzo de 2001 0:04
Para: [EMAIL PROTECTED]
Asunto: [PATCH][tc3.3]Re: Proposed ApacheConfig.java change
{sorry about the resend - I hit the send button early
last time}
The attached PATCH modifies
org.apache.tomcat.modules.c
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
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):
You don't need a "strong" vote - I'll do the change :-)
2) Configuration of mod_jk is
FYI:
I'm pretty much done with the mods I wanted to make (I
ended up adding a few extras) and am in the testing
and documenting phase. Should be ready tomorrow.
BTW: I figured out soon after my last post that the
only thing I needed to do enable auto-generation of
apache config files was to
Hi y'all.
I'm in the process of making a small tweak so that the
mod_jk.conf-auto file uses IfModule conditionals
around the LoadModule statments. As discussed
earlier, there should be a lot of deployment
configuration value in this tweak.
However, after upgrading to the latest and greatest
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
