-
15. Re: EntityHome @PerNestedConversation
luxspes Oct 1, 2008 11:43 PM (in response to sducas.sducas1.gmail.com)Puzzling good news Stephane!
It seems all that has to be done to fix this is modify the code in org.jboss.seam.framework.Home and use the transient incantation to stop the black magic.
Now the reminding question is: Why?
-
16. Re: EntityHome @PerNestedConversation
luxspes Oct 3, 2008 4:32 PM (in response to sducas.sducas1.gmail.com)Now JBSEAM-3493 has a simple seam-gen based example project showing the problem.
-
17. Re: EntityHome @PerNestedConversation
luxspes Dec 8, 2008 6:33 PM (in response to sducas.sducas1.gmail.com)I am reading in seam21migration.txt that:
Seam's ManagedEntityInterceptor (formally ManagedEntityIdentityInterceptor) is now disabled by default.Did this had anything to do with JBSEAM-3493? Has anyone tried to see if JBSEAM-3493 was accidentally fixed by the removal of ManagedEntityIdentityInterceptor?
Regards,
-
18. Re: EntityHome @PerNestedConversation
luxspes Dec 8, 2008 7:39 PM (in response to sducas.sducas1.gmail.com)Yes...Yes!, Yes!! JBSEAM-3493 is fixed in Seam 2.1.0.SP1, but only if ManagedEntityInterceptor is disabled:
<core:init debug="true" jndi-pattern="@jndiPattern@" > <core:interceptors> <value>org.jboss.seam.core.SynchronizationInterceptor</value> <value>org.jboss.seam.async.AsynchronousInterceptor</value> <value>org.jboss.seam.ejb.RemoveInterceptor</value> <value>org.jboss.seam.persistence.HibernateSessionProxyInterceptor</value> <value>org.jboss.seam.persistence.EntityManagerProxyInterceptor</value> <value>org.jboss.seam.core.MethodContextInterceptor</value> <value>org.jboss.seam.core.EventInterceptor</value> <value>org.jboss.seam.core.ConversationalInterceptor</value> <value>org.jboss.seam.bpm.BusinessProcessInterceptor</value> <value>org.jboss.seam.core.ConversationInterceptor</value> <value>org.jboss.seam.core.BijectionInterceptor</value> <value>org.jboss.seam.transaction.RollbackInterceptor</value> <value>org.jboss.seam.transaction.TransactionInterceptor</value> <value>org.jboss.seam.webservice.WSSecurityInterceptor</value> <value>org.jboss.seam.security.SecurityInterceptor</value> <!-- Disable ManagedEntityInterceptor <value>org.jboss.seam.persistence.ManagedEntityInterceptor</value>--> </core:interceptors> </core:init>
If I enable it again, JBSEAM-3493 comes back to attack us with its black magic! So I guess this demonstrates that ManagedEntityInterceptor and PerNestedConversation are incompatible!
-
19. Re: EntityHome @PerNestedConversation
luxspes Dec 8, 2008 7:52 PM (in response to sducas.sducas1.gmail.com)Hi!
Just uploaded a new example project in JBSEAM-3493. Can anyone else please confirm the ManagedEntityInterceptor/PerNestedConversation incompatibility?
Regards,