[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1656) passivated entities in parent conversations cause version problems when they're updated

[Matt Drees (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1656?page=all ]

Matt Drees updated JBSEAM-1656:
-------------------------------

    Attachment: EntityPassivationTest.java
                Thing.java

A SeamTest that shows the problem. 

Also, I added a test to check that a StaleStateException is thrown when an entity is modified in another conversation, but no exception gets thrown.  Let me know if that's an actual real problem and if you want me to open another jira for it.  Of course, maybe I just don't understand what is supposed to be happening, so feel free to just delete the second test.

Note that this won't immediately run when dropped into jboss-seam/src/test/misc; somehow a managed persistence context and a entityManagerFactory need to be configured.  I didn't try to solve that problem, because I don't know how you want your test directory structured.

> passivated entities in parent conversations cause version problems when they're updated
> ---------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-1656
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1656
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0.BETA1
>         Environment: current cvs
>            Reporter: Matt Drees
>         Assigned To: Gavin King
>            Priority: Blocker
>             Fix For: 2.0.0.CR1
>
>         Attachments: EntityPassivationTest.java, Thing.java
>
>
> If an entity in a parent conversation is updated and the persitence context is flushed, it gets a new version.  However, the passivatedEntity in its EntityBean wrapper still has the old version.  The wrapper is not passivate()ed at the end of the request, because it's not in the current conversation.  So, when the nested conversation ends and the wrapper is activate()ed at the beginning of a request, the version mismatch causes a StaleStateException.
> See the forum post for more details.

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