Hi guys, I'm stuck with a JNDI resource object factory problem. Hopefully you can help me out with this issue.
My idea was to provide multiple web applications running inside a Tomcat instance with configuration properties from config files located outside the WAR file of the applications. I'm currently trying to provide these configuration properties with a global naming resource (defined inside the server.xml) which is consumed by the said applications to keep the configuration container independent and to avoid direct file access from a web application. So far almost everything already works perfectly! Except that Tomcat obviously caches resources which are looked up via JNDI. This way I have to restart Tomcat every time the external config files changes because the web applications never access my ObjectFactory again after Tomcat has cached the result of the ObjectFactory. Accordingly to the documentation an implementation of ObjectFactory should be accessed each time a web application looks it up with its JNDI key. But that's definitely not the case here. Any ideas or thoughts on this issue? Is there any way to disable this behavior of Tomcat's JNDI resource management? Or any comments on this plan to externalize the application configuration in general? Thanks in advance! Marco --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
