Yes I do, and am using EJB3.0 entity and session beans. I had the problem, where my session beans couldn't load the EntityManager. That was because I had mapping issues with my EntityBeans, which showed up in my log.
If the tables can't be created, then your entity beans can't be initialized. Ergo, your EM won't be bound. If you already have your tables in your DB, turn off hbm2ddl. It looks like you have it set at "create-drop". Every time you deploy your application, it will try to drop your tables, and recreate them. Is this running on a production server? If not, change your log settings to the following: org.jboss.EJB3 = DEBUG org.hibernate = DEBUG Redeploy your app, and view the server log. Maybe that will give you more insight. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3901843#3901843 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3901843 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
