DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28158>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28158 Context reloadable="true" not working if autodeploy="false" ------- Additional Comments From [EMAIL PROTECTED] 2004-04-05 11:58 ------- > "don't use server.xml, use a context file with a name matching the context name" Ok Remy. I've really tried everything now. Even with the Context-definition in a seperate .xml file realoding doesn't work if autodeploy is true. I tried every possible combination of autodeploy, deployonstartup and context-paths. I can list the different attemps on détail if you want me to. The result in the end is always the same: if you don't turn on autodeploy auto-reloading will not work! I don't say that there is a direct link between those two. But I suspect that there is a different loader attached (or no loader at all) to the context if its deployed directly (by specifying context in the server.xml or in a specific context-xml) than if its deployed by the auto-deployer. So one of those "if"'s here would not be true because of this. if (getLoader() != null) { // <-- no loader attached? if (reloadable && (getLoader().modified())) { // .modified() never returns true for attached loader If you still think I'm wasting your time with this I'll have a closer look at the code myself, but obviously it would be much easier for you to find the problem. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
