[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3049) javax.persistence.EntityNotFoundException on activating passivated entities that have been deleted

Alex Savitsky (JIRA) jira-events at lists.jboss.org
Thu May 29 10:27:45 EDT 2008


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

Alex Savitsky updated JBSEAM-3049:
----------------------------------

    Attachment: test.2.0.2.SP1.war

Test case, BROKEN for 2.0.2.SP1 (GA, too). Same instructions as for 2.0.1, except it will now throw an exception when delete button is pressed.

> javax.persistence.EntityNotFoundException on activating passivated entities that have been deleted
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-3049
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-3049
>             Project: Seam
>          Issue Type: Bug
>    Affects Versions: 2.0.2.GA, 2.0.2.SP1
>         Environment: Tomcat 5.5
>            Reporter: Alex Savitsky
>         Attachments: test.2.0.1.GA.war, test.2.0.2.SP1.war, Test.zip
>
>
> Basically, as of 2.0.2, whenever Seam attempts to activate a passivated entity (say, via the ManagedEntityIdentityInterceptor) that has been deleted during the last action, it throws a javax.persistence.EntityNotFoundException. Previously (2.0.1), these cases have been handled correctly. The culprit is the HibernatePersistenceProvider.getClassMetadata - it was using Seam.getEntityClass, but switched to its own getEntityClass in 2.0.2, which uses Hibernate.getClass, that apparently doesn't like to encounter deleted entities...

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

        



More information about the seam-issues mailing list