-Ursprüngliche Nachricht-
Von: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Gesendet: Freitag, 17. August 2012 15:50
An: Tomcat Users List
Betreff: Re: hostConfigClass attribute
2012/8/16 Schulz-Hildebrandt, Ole ole.schulz-hildebra...@ppimedia.de:
Hi,
I'm working
Hi Mark,
thanks for your reply. I'm now using a custom Host implementation. Instead of
adding the hostConfigClass attribute etc. I overwrote addLifecycleListener
(replacing the default HostConfig by my custom HostConfig) so I am also no
longer dependent on this hostConfigClass rule.
Best
2012/8/16 Schulz-Hildebrandt, Ole ole.schulz-hildebra...@ppimedia.de:
Hi,
I'm working with tomcat 7.0.29. In tomcat 5.x.x it was possible to use a
custom HostConfig class by setting the hostConfigClass attribute at a Host
element in the server.xml. This allowed to customize the order
Hi,
I'm working with tomcat 7.0.29. In tomcat 5.x.x it was possible to use a custom
HostConfig class by setting the hostConfigClass attribute at a Host element
in the server.xml. This allowed to customize the order webapps were started, to
avoid deploying of webapps at tomcat startup etc
On 16/08/2012 16:03, Schulz-Hildebrandt, Ole wrote:
Hi,
I'm working with tomcat 7.0.29. In tomcat 5.x.x it was possible to
use a custom HostConfig class by setting the hostConfigClass
attribute at a Host element in the server.xml. This allowed to
customize the order webapps were started
