On 14/01/2010 22:19, youngm wrote: > I personally don't like any of the options. If you articulated your concerns, then we might be able to show you solutions to them.
> Here are a couple of solutions > that I might like a little more. I'd be curious if anyone likes any of > these. > > 1. modify the tomcat startup scripts to provide a standard hook for adding > to the system classloader (CATALINA_CLASSPATH)??? Very bad idea. Search the archives for a long list of things that go wrong when you start changing the class path. Not to mention that would make the new driver visible to all web applications not just the web app that needed the new jar file. And you'd need to restart Tomcat for the changes to take effect. That means downtime unless you use load-balancing. > 2. Add an optional Classloader similar to the common.loader that is > positioned between the system loader and the webapp loader. This loader > could be configured the same way the common.loader is configured through a > catalina.properties property? Won't help. The servlet spec requires that classes in the web application take priority. > Thoughts? Even if the solutions would work (which they won't) they seem a lot more complex than - unpack war - replace driver jar - pack war - deploy through manager That would update the driver for the app with zero downtime. What is the issue with this approach? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
