Good morning, I'm still trying to figure out how I can cause tomcat to re-read JNDI resources. Here is one way I found out earlier:
> After further tests I found out that the server will reload JNDI data > sources if all the following steps are performed: > 1. Change the configuration > 2. Execute _any_ servlet or jsp using the eclipse command "Run As... > > Run on Server" > 3. Restart Tomcat As you can see, this only works from within Eclipse, and I have no clue how I could cause a JNDI reload in a production environment. In the meantime, I tried some further things, e.g. updating the last-modified-date of web.xml to cause a redeploy. I also did some more googling, but to no avail. Does anybody know a way to cause Tomcat to rebuild the JNDI context of an application? Or is there a better way to dynamically configure Data Sources? Any ideas are welcome. In the worst case I'd need to fall back on a custom config file and database connections using DriverManager, but this would destroy all benefits of pooled connections etc :-( Thanks, Jonas --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
