After some tests, it seems you are wrong. I had a call to a session bean method explicitly through an interface that was annotated as @Local. The call passed a non-serializable Entity bean as a parameter. This worked OK. (Caller and callee are part of the same application and are in the same JAR, in the same EAR, in other words, a local call is possible).
However, when I added the @Remote annotation, I started getting a NonSerializableException. Serialization is only needed for the Remote call. Therefore, when I have both annotations it seems that @Local is just ignored, at least on JBoss. Someone from the JBoss team cares to answer if this is the expected behavior or if we have a bug here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947836#3947836 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947836 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
