That does sound strange...
check however your tmp dir for old deployments. I don't know how it could be picking those up though.
Hmm.. I found out what was happening, but it still seems strange to me. Perhaps the behaviour of the classloader changed from Jboss 3.0.6 to 3.2.2 ?
Here's what is happening, we have a webapp deployed as test.war. In the same /deploy folder there is a webapp, test2.war.
test2.war is an old copy of test.war that some developer left around. When touching the web.xml in test.war, we suddenly find that a number of the classes being picked up are those from test2.war.
I also noticed this in another instance, where I had two classes with the same package and name, in two different webapps. The method signatures for one was a superset of the other. However, when trying to invoke those methods, the JSP compiler would complain about the method being an undefined symbol. So it appears that though I was working from webappA, it was picking up the class in webappB.
Is there something significantly different in the way classloading was chagned in 3.2.2? I suppos I need to RTFM, but if there is a quick answer -- that would help greatly!