thanks, the test fails here also.. i hope someone finds the cause of this soon
i want to set something straight from my previous post though. i said that the exception did not happen for all data. i found that kinda strange, so i checked again. i noticed it does happen for all data, but not when the attribute is null, which seems logical. still doesn't happen in a web start environment using the same jars thought. the only difference is that they are signed in the webstart env. could that have something to do with it ? concercing the exception on the server when passivating, i think it's actually the same problem, as i only have problems with stateful session bean if they work with obejcts that can have lazy attributes. maybe they can't be serialized for passivation, and that's why an exception occurs ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923312#3923312 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923312 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
