[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3049) javax.persistence.EntityNotFoundException on activating passivated entities that have been deleted
[ http://jira.jboss.com/jira/browse/JBSEAM-3049?page=all ]
Pete Muir updated JBSEAM-3049:
------------------------------
Fix Version/s: 2.0.x
2.1.0.BETA1
Priority: Blocker (was: Major)
Argh. Thanks for spotting this!
We want to use Hibernate where possible to establish the entity class (as it allows
classes to be mapped e.g. via .hbm.xml) but to fall back cleanly to less better methods
when it can't tell us the class.
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
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...
--
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