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

[Dan Allen (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-2983?page=comments#action_12414119 ] 
            
Dan Allen commented on JBSEAM-2983:
-----------------------------------

Well, @BypassInterceptors could cut out the interceptors being added, but I believe that still leaves you with a proxy.

Is there some way we can detect an entity without @Entity? Is this something Hibernate can detect? SessionFactory#getClassMetadata()?

> Unknown Entity when persisting seam managed JPA entity
> ------------------------------------------------------
>
>                 Key: JBSEAM-2983
>                 URL: http://jira.jboss.com/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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira