Clarification: it doesn't seem to matter if the .jar is included in the ear or not. It
seems that we get the exception when the classes are loaded in the context of an ear. In
that ear we use the jboss-app to specify a particular ClassLoader - the one that loaded in
JBoss Messaging.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029796#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...