On 01/11/2011 22:31, Konstantin Kolinko wrote: > 2011/11/2 Mark Thomas <[email protected]>: >> On 01/11/2011 22:01, Konstantin Kolinko wrote: >>> 2011/11/2 Konstantin Kolinko <[email protected]>: >>>> 2011/11/1 Mark Thomas <[email protected]>: >>>>> My current thinking is to add redeployResoucre and reloadResource to >>>>> Context and deprecate watchedResource, making it a synonym for >>>>> reloadResource. Thoughts? (I haven't tested this yet.) >>>>> >>>> >>>> Are you talking about API or about Configuration? >>>> >>>> <WatchedResource> in conf/context.xml defaults to WEB-INF/web.xml. It >>>> is a news for me that it covers context.xml as well. >>>> >>>> I think web.xml triggers reload, context.xml triggers redeploy. >> >> That is what I expected too but it isn't what happens. See line ~575 in >> ContextConfig. I've checked the history and it has been that way all the >> way back to 2004. > > Oh, I see. Looking at 5.5 > // Add as watched resource so that cascade reload > occurs if a default > // config file is modified/added/removed > > I think it talks about the "default" context file that is > $catalina.base/conf/context.xml. That explains why it says about > "cascade". > > I am OK with that triggering a reload, but as you noted that seems to > not work as Context is not recreated. > > I think webapp's own Context file should be a different beast.
Changes to any context.xml have to trigger a redeploy else they won't take effect as no new Context object will be created. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
