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

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

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: PatchedPersistenceProvider.java, 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...

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 Assigned To: Pete Muir Priority: Blocker Fix For: 2.1.0.BETA1, 2.0.x Attachments: PatchedPersistenceProvider.java, 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...

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.SP1, 2.0.2.GA Environment: Tomcat 5.5 Reporter: Alex Savitsky Assigned To: Pete Muir Priority: Blocker Fix For: 2.0.x Attachments: PatchedPersistenceProvider.java, 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...

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.SP1, 2.0.2.GA Environment: Tomcat 5.5 Reporter: Alex Savitsky Assigned To: Pete Muir Priority: Blocker Fix For: 2.0.x Attachments: PatchedPersistenceProvider.java, 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...