Christoph,
In Tomcat 3.3, I would recommend the following steps
1. Copy and rename the ApacheConfig.java, say MyApacheConfig.java
for example purposes.
2. Implement your functionally in MyApacheConfig.java
3. Compile MyApacheConfig.java and put the class in a jar file.
4. Put the jar in Tomcat 3.3's "lib/container" directory.
5. Add a line to the "conf/modules.xml" file containing:
<module name="MyApacheConfig"
javaClass="org.apache.tomcat.modules.config.MyApacheConfig"/>
6. Replace the "<ApacheConfig .../>" with "<MyApacheConfig ...>" in
the server.xml.
Not having to rebuild Tomcat to incorporate your customization
is one of the advantages of Tomcat 3.3 over 3.2.x, and one of its
primary goals.
Cheers,
Larry
> -----Original Message-----
> From: Christoph Schönfeld [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 11, 2001 9:22 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Configuration of config-auto contents
>
>
> I had already feared what you are stating. Is this class easy
> to put in
> place? Does it interfere with the Tomcat distribution (complicating
> installation and updates)? How is it invoked?
>
> Sorry for all these questions. ;-)
>
> Thanks,
> Christoph
>
> Larry Isaacs wrote:
> > I think the only way to get what you want is to customize
> > the source for the ApacheConfig class. In Tomcat 3.3
> > this is a replaceable module, i.e. use MyApacheConfig
> > instead of ApacheConfig. I can supply more detail if
> > desired.
> >
> > Larry
>
