It may be that some entity bean in the middle has failed to deploy due to a mistake in the EJB-QL and other beans depend on it. I've had the same problem.
The bean that was throwing the exception at creation time was fine. The culprit was elsewhere. Check the EJB-QL sentence parsing of all your entity beans (in DEBUG mode) and see one has failed. Cheers, Ivan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876124#3876124 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876124 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
