Hot Deploying Class Files

Long story short, I've got a handful of class files that I need to deploy into a running webapp in Tomcat 6. I've copied them to the right location and made sure the permissions were right. I've deleted everything in the work directory and I've bounced tomcat. I'm still getting results from the old class files. What am I missing?

Does the Context have it's reloadable property set?
Also, and I've gone absolutely batcrap crazy trying to figure this out myself once, the risk of deploying individual class files is that they might contain public static final members that have changed, which you might expect would be picked up. Except if you don't recompile a class that uses the changed 'constant' of another class, it will still use the old value, because they're copied into the .class file's constant pool during compilation.

Jelle Klap wrote:Does the Context have it's reloadable property set?
Also, and I've gone absolutely batcrap crazy trying to figure this out myself once, the risk of deploying individual class files is that they might contain public static final members that have changed, which you might expect would be picked up. Except if you don't recompile a class that uses the changed 'constant' of another class, it will still use the old value, because they're copied into the .class file's constant pool during compilation.

No, reload-able isn't set (which should mean false). I'm thinking it might be a spring thing. This is a service class that is loaded (singleton) by spring. But I thought kicking tomcat would take care of it. Not sure why / how that context would be being held onto.