From: Marc P. <ma...@an...> - 2003-07-24 10:33:21
|
On Thu, 24 Jul 2003 11:56:29 +0200, Sebastian Kanthak <seb...@mu...> wrote: > I've tried to track this down the last two hours, but I have no clue. I > did the following to get a minimal test case. Sebastian, thanks for spending some time on it! The error you get is different probably just because I am based on WMServlet and you are based on Standalone. This is very strange though, because we know for a fact that other JARs are reloaded fine in Tomcat and Resin. So there must be something specific to webmacro.jar that is different. It does not look like some strange classloader usage issue -within- WM code though, which was possible with my flavour of the problem, because yours is a class loading (rather than resource) problem. The "touch" working without problem sounds to me like there might be some intelligence going on in the classloader, or because no code has actually changed it continues to work with the previous code on the previous classloader perhaps. This is all speculation but that's all we have right now! I'll see if I can see anything in the way the jar is built. I know, I must be crazy... but maybe its a problem with reloading zipped JARs vs unzipped jars for example. Marc -- Marc Palmer Contract Java Consultant/Developer w a n g j a m m e r s java and web software design experts with an ethical outlook http://www.wangjammers.org |