Based on the log it is the problem with EJB3. AFAIK, JBoss 4.2.2 has a major restructuration on EJB3 which mostly is done by the Seam team.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099708#4099708 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4099708 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
