On Sun, Oct 4, 2009 at 1:02 PM, Rasmus Larsen <kolibria...@gmail.com> wrote: > 2009/10/4 Leon Rosenberg <rosenberg.l...@googlemail.com>: >> On Sun, Oct 4, 2009 at 1:00 AM, Eric B. <ebe...@hotmail.com> wrote: >>> "Caldarale, Charles R" <chuck.caldar...@unisys.com> wrote in message >> Back to the original post, >> why don't you simply patch (maybe automatically with ant) the jar file >> containing the 'old' version of the class and remove it? > > The jar files are provided and signed by an external vendor. > >> You won't be able to keep two different versions of a class in the >> same classloader anyway. > > I want to use the newest version only, of course. Normally, I would > simply place the jar with the newest versions first in the classpath. > But the tomcat server has no such control, instead it just loads jar > files from the WEB-INF/lib directory, which means that the order is > based on the OS filesystem.
No, you can just overwrite setclasspath.sh and put the 'first' jar into the first place of the classpath manually. On a side note, I would have a serious discussion about the quality of their jars with the vendor(s). Simply put: one class can only be located in one jar, everything else is unacceptable :-) regards Leon --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org