Changing entityNamePattern generates bad code
---------------------------------------------
Key: HIB-200
URL: http://jira.andromda.org/browse/HIB-200
Project: Hibernate Cartridge
Type: Bug
Versions: 3.2-RC1
Reporter: Art Pope
Assigned to: Carlos Cuenca
Changing the Hibernate cartridge's entityNamePattern property to anything other
than its default of {0} results in code being generated with numerous errors.
For example, if entityNamePattern is {0}Entity, then entity Account's abstract
class will be named AccountEntity, but AccountEntity.Factory.newInstance() will
be declared as returning an Account (not AccountEntity). A 1-1 association with
Account will be declared as a property of type Account rather than
AccountEntity. Similarly, a 1-n association with Account will be declared as
java.util.Collection<Account> rather than java.util.Collection<AcountEntity>.
A similar problem was reported against the Spring Cartridge in Sep 2006 here:
http://galaxy.andromda.org/jira/browse/SPRING-115?page=comments.
--
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
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
