[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2121) Support for an SMPC per nested conversation
[ http://jira.jboss.com/jira/browse/JBSEAM-2121?page=all ]
Jacob Orshalick updated JBSEAM-2121:
------------------------------------
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.
was:
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.
Support for an SMPC per nested conversation
-------------------------------------------
Key: JBSEAM-2121
URL: http://jira.jboss.com/jira/browse/JBSEAM-2121
Project: JBoss Seam
Issue Type: Feature Request
Affects Versions: 2.0.0.CR2
Reporter: Jacob Orshalick
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.
--
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