Seam-managed persistence contexts and REQUIRES_NEW -------------------------------------------------- Key: JBSEAM-1491 URL: http://jira.jboss.com/jira/browse/JBSEAM-1491 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.3.0.GA It's always wrong to try and propagate a PC across REQUIRES_NEW. But indeed that is exactly what Seam does with conversation scoped PCs. Of course, the correct thing to do is use @PersistenceContext in this case. But how many users know they are supposed to do this? Is there some way we can *detect* this problem? We should at the very least document it... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira