[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2983) Unknown Entity when persisting seam managed JPA entity

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated JBSEAM-2983:
------------------------------


This is going to be very hard to do in Seam 2.

The component type is needed at bootstrap, and we don't have access to PersistenceProvider at that point to abstract out the call to Hibernate to discover whether the class is a hbm mapped entity.

I guess we could hack it in, but is it really worth it?

> Unknown Entity when persisting seam managed JPA entity
> ------------------------------------------------------
>
>                 Key: JBSEAM-2983
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-2983
>             Project: Seam
>          Issue Type: Bug
>    Affects Versions: 2.0.1.GA
>            Reporter: Guillaume Jeudy
>            Priority: Minor
>             Fix For: 2.1.0.BETA1
>
>
> Caused by: java.lang.IllegalArgumentException: Unknown entity: com.archinsurance.rdm.entity.packages.impl.RefReleasePackageImpl_$$_javassist_4
> 	at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:215)
> when attempting to persist a seam managed JPA entity. Seam instantiates a javassist proxy and this is what the user app is trying to persist.
> The exception is not thrown when the entity is marked with @Entity annotation, if it is mapped with XML hibernate mapping definition it will fail with the above exception.
> Implement a consistent behavior to handle the seam managed JPA entity usecase regardless of the mapping technique being used. As recommended by Pete Muir this use case should not be utilized. 
> Suggested behavior should be to throw a more explicit exception on startup whenever this invalid usecase is detected.
> More details in the below forum thread:
> http://seamframework.org/Community/UnknownEntityWhenPersistingSeamManagedJPAEntity

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira