Sorry again, folks -- false alarm! Turns out I was including jbossall-client.jar on the list of resources in my application's JNLP file, and apparently that jar contains the old remoting code, which caused the exception.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021171#4021171 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021171 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
