Use orm.xml file to define entities
-----------------------------------
Key: EJB-113
URL: http://jira.andromda.org/browse/EJB-113
Project: EJB Cartridge
Type: Improvement
Environment: AndroMDA 3.4-SNAPSHOT + EJB3 cartridge
Reporter: Olivier THIERRY
Assigned to: Vance Karimi
Priority: Critical
The way the EJB3 cartridge works today, named queries, unique constraints and
table name for entities are defined using annotations. If you model a transient
method on an entity in your model, these annotations will be added to a class
generated once in src/main/java directory. It means if you change the table
name for the entity, add or update a named query, it will not be token in
account by AndroMDA, you will have to change the classes in src/main/java by
hand. Not acceptable for a MDA too !
To avoid this, I made some changes to EJB3 cartridge so that annotations at
entity level (@Table, @NamedQuery, ...) are replaced by tags in orm.xml file.
Annotations are still used to define entity columns.
More infos on this topic of the forum :
http://galaxy.andromda.org/forum/viewtopic.php?t=4946
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
