I have also experienced this -- seems like jboss serialization cannot handle the uninitialized lazy attributes (ClassCastException in ClassReferencePersister.java:42). In my case I can work around it for the time being by using a local interface on the same machine, but I can see how this is an issue for remote interfaces. It would probably be nice if they get serialized but just omit the lazy stuff, and the your coding contracts understand this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922415#3922415 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922415 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
