Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-1491

Seam-managed persistence contexts and REQUIRES_NEW

    Details

    • Type: Task
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: The future
    • Component/s: Core
    • Labels:
      None

      Description

      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...

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  gavin.king Gavin King
                  Reporter:
                  gavin.king Gavin King
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated: