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. Though this is still possible
in tomcat 7.0.29 (internally still a LifecycleListenerRule for the
hostConfigClass attribute is registered at the Digester) a warning is outputted
(because the method setHostConfigClass was removed from the StandardHost):
WARNUNG: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
'hostConfigClass' to 'de.ppimedia.tomcat.hostconfig.AppControllerHostConfig'
did not find a matching property.
Does anybody know why this method was removed? Is hostConfigClass only a
"internal" attribute in tomcat 7.x.x? If so is there a "correct" way to use a
custom HostConfig?
Best regards,
Ole
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
