[
http://jira.jboss.com/jira/browse/EJBTHREE-929?page=all ]
Venkat Kakula updated EJBTHREE-929:
-----------------------------------
Priority: Critical (was: Major)
SQL Exception when entities with composite keys are retrieved
-------------------------------------------------------------
Key: EJBTHREE-929
URL:
http://jira.jboss.com/jira/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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira