Wednesday, June 20, 2007 11:53 AM
Just a thought - may be way off...
Maybe there's a jar in your server that's the same one (but different version) than the one in your app. The server could be set to first try to load its own version before checking for one in your app.
Happened to me using JBoss 3.2 with commons-collections.jar.
I tried to set JBoss to look to my app for the jar before using its own, but it never worked. I ended up just updating the one in JBoss' lib dir.