Anonymous | Login | Signup for a new account | 12-17-2024 10:53 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001622 | [Resin] | major | always | 02-21-07 12:58 | 03-29-07 13:30 | ||||
Reporter | jarnbjo | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 3.1.1 | Product Version | 3.1.0 | ||||
Product Build | |||||||||
Summary | 0001622: Amber fails if entity classes are referred in <resource> tags in dep. descriptor. | ||||||||
Description |
I have the following situation: I am declaring and configuring different objects in the deployment descriptor using <resource> tags. These classes are directly or indirectly referring to persistent entity classes (annotated with javax.persistence.Entity). In this case, the Amber enhancement of these classes seem to be skipped. The database tables are created (if not already present), classes are generated in work/pre-enhance, but work/post-enhance is not even created and trying to use the classes through the entity manager causes the following exception to be thrown: java.lang.IllegalArgumentException: persist() operation can only be applied to an entity instance. If the argument is an entity, the corresponding class must be specified in the scope of a persistence unit. If I remove the <resource> tags from the deployment descriptor, the entity classes are enhanced and the persistence API works as expected. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 26 unique queries executed. |