I found the solution. In fact, it is a bug in the EJB3.0 implementation. It has been fixed in the EJB3.0RC9 version. http://jira.jboss.com/jira/browse/EJBTHREE-628
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978696#3978696 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978696 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
