2011/11/2 Mark Thomas <ma...@apache.org>:
> On 01/11/2011 22:01, Konstantin Kolinko wrote:
>> 2011/11/2 Konstantin Kolinko <knst.koli...@gmail.com>:
>>> 2011/11/1 Mark Thomas <ma...@apache.org>:
>>>> 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.
>
>> Touching webapps/myapp.war also triggers a redeploy and not a reload.
>
> I'm fine with that. An updated WAR may include a new context.xml file.
>
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
