[jboss-user] [JBoss Seam] - Re: Possible bug - POJO doesn't automatically join transacti

2007-04-04 Thread ASavitsky
Ok, thanks for the clarification. So, as I understand it, managed transactions give me a transaction around the method, and managed PCs give me an injected EM - but this doesn't mean that the EM automatically joins the transaction? Searched the reference docs, but haven't found any mention on

[jboss-user] [JBoss Seam] - Re: Possible bug - POJO doesn't automatically join transacti

2007-04-04 Thread petemuir
Take a look at http://www.hibernate.org/hib_docs/entitymanager/reference/en/html/transactions.html#d0e1841 - I doubt it's to do with whether the entity is managed or not, but to do with the transaction/em lifecycle up to that point. But I'm not an expert. View the original post :

[jboss-user] [JBoss Seam] - Re: Possible bug - POJO doesn't automatically join transacti

2007-04-03 Thread petemuir
n.b. EntityHome.persist calls getEntityManager.joinTransaction(); It's working correctly for me anyway. Post all the exceptions in the error log View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4034254#4034254 Reply to the post :

[jboss-user] [JBoss Seam] - Re: Possible bug - POJO doesn't automatically join transacti

2007-04-03 Thread ASavitsky
EntityHome.persist might call joinTransaction, but EntityController.persist (which I use) certainly does not. Anyway, here's the stack trace: ERROR [org.jboss.seam.web.ExceptionFilter] - uncaught exception | javax.servlet.ServletException: Error calling action method of component with id

[jboss-user] [JBoss Seam] - Re: Possible bug - POJO doesn't automatically join transacti

2007-04-03 Thread petemuir
Ok, sorry, I didn't read your post carefully enough. If you are using a Seam JavaBean component, then you aren't running in a managed environment (apart from what @Transactional gives you [1]), so it's your job to call joinTransaction() as the conversation scoped EntityManager may have been