WAR not deploying properly, despite logging showing so

[ahardy66]

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

[starksm64]

If its a jsp page using the class its jsp file needs to have its timestamp updated in order to trigger recompilation of the page to see the change. The previous servlet class will be used and its use of constants is embedded in the servlet class file.

[ahardy66]

It's not a JSP. Both times involved struts action subclasses, being called by the struts action servlet.

However this sounds like it would cause exactly the problem I am seeing, if it also affects other classes rather than just JSPs. But I can't see any other classes being cached anywhere like the JSPs.

[erik777]

I think I had this problem a long time ago, and resorted to recompilling all classes. I'm not sure it was the same problem, but recompilling all classes instead of only those I modified did solve a problem for me.

[tomerbd]

Have a look at :
$JBOSS_HOME\server\$CONFIGURATION\conf\jboss.web\localhost\*

I had some similar problems like you have and after deleting those files I coudl successfuly redeploy my .war's