JBossDeveloper

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?

Now JBSEAM-3493 has a simple seam-gen based  example project showing the problem.

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,

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!

Hi!

Just uploaded a new example project in JBSEAM-3493. Can anyone else please confirm the ManagedEntityInterceptor/PerNestedConversation incompatibility?

Regards,