I was caught out twice today by a deployment problem with my WAR file in tomcat.
It seems JBoss is caching the classes from the old WAR somewhere and only replacing the updated classes from the new WAR, not the whole thing. I changed some constants in my global constants class for my app, compiled and packaged it as a war and deployed it. JBoss killed my session, made me do a new login and also logged a bunch of tomcat messages about contexts loading. However my changes had no effect. I searched for ages for the reason, and finally altered a class which uses the Constants class, putting in a debug statement. I recompiled & deployed and suddenly my changes to the Constants class worked. This happened again just now. How can I avoid this sort of caching of the old war? Apart from recompiling my whole app? Thanks Adam View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830770#3830770 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830770 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
