Like I said, you might have a stray copy of the class somewhere. I am always amazed at where those things hide. I once ran into an issue where an older version of a class appeared in the JVM endorsed directory. I tracked it down to someone who was too lazy to figure out how to set the classpath correctly, so he just copied the jar file there, I definitely gave him a piece of my mind. I was going nuts trying to find out why my code worked on some machines but not on others. It was -verbose:class that finally pointed out where the extra copy of the class was located. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015104#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...