You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/05/14 16:13:30 UTC
DO NOT REPLY [Bug 19852] -
When context reloaded the Parameters specified in server.xml for the Context are not availaple
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19852>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19852
When context reloaded the Parameters specified in server.xml for the Context are not availaple
------- Additional Comments From mihy@q8.dk 2003-05-14 14:13 -------
Further snooping around in the code has directed me in the direction of the
ContextConfig class. When a lifecycle STOP_EVENT is recieved by ContextConfig
it removes all ApplicationParameters from the StandardContext. On the other
hand, when a lifecycle START_EVENT is fired by the StandardContext only the
Parameters from WEB-INF/web.xml and conf/web.xml are added to the
StandardContext but not server.xml <Parameter> elements. Since this is the way
ContextConfig functions at the present a quick fix would be to remove the call
in ContextConfig.stop() to context.removeApplicationParameter().
Perhaps this has side-effects that I am unaware of but it seems to work fine
here.
/Mikkel
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org