[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-929) SQL Exception when entities with composite keys are retrieved
[
https://jira.jboss.org/browse/EJBTHREE-929?page=com.atlassian.jira.plugin...
]
Carlo de Wolf resolved EJBTHREE-929.
------------------------------------
Resolution: Out of Date
This issue is reported against a version which is no longer maintained,
which means that it will not receive a fix. As a result we are closing
this bug.
If you can reproduce this bug against a currently maintained version of
JBoss EJB 3 please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
SQL Exception when entities with composite keys are retrieved
-------------------------------------------------------------
Key: EJBTHREE-929
URL: https://jira.jboss.org/browse/EJBTHREE-929
Project: EJB 3.0
Issue Type: Bug
Environment: Windows XP SP2; JBoss 4.0.5 GA with EJB 3.0
Reporter: Venkat Kakula
Priority: Critical
After migrating an OC4J/TopLink Essentials project to JBoss/Hibernate, there were some
breakdowns. I have some entities with composite keys (specifically - 4 ID fields). There
is a separate ID Key class. These field names do not match the database fields directly
but are mapped with @Column(name="A_B_C" nullable="false") style
notation with the field names as aBC. The SQL generated thus looks for
'TABLEONE0_'.'aBC' specifically on the ID fields of the entity instead of
'TABLEONE0_'.'A_B_C' they should be mapping to. The rest of the attributes
map out alright.
By the way I just wanted to note that all the code that is breaking down was working fine
on OC4J with toplink - FYI.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira