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

Support for an SMPC per nested conversation

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate Issue
    • Affects Version/s: 2.0.0.CR2
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      Currently an open issue and ongoing discussion with respect to the existing nested conversation implementation is master-details editing. If a Seam-managed Persistence Context (SMPC) is shared between the outer and nested conversation, any changes made in the nested conversation will be flushed by the SMPC in the outer conversation and vice versa if a flush is initiated. Support for initialization of a new SMPC within a nested conversation would allow state changes in the nested conversation to be confined to that conversation, thus resolving this issue. Perhaps something like the following could be supported:

      <persistence:managed-persistence-context name="bookingDatabase"
      auto-create="true"
      per-nested-conversation="true"
      persistence-unit-jndi-name="java:/EntityManagerFactories/bookingData"/>

      It would also be nice to be able to use annotations (i.e. something similar to @PerNestedConversation).

      For further information on this approach please see the forum posting. Thanks.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  jacob.orshalick Jacob Orshalick
                • Votes:
                  6 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: