users@glassfish.java.net

Re: Latest version of Toplink Essentials problem with bidirectional one-man

From: <glassfish_at_javadesktop.org>
Date: Thu, 04 Oct 2007 07:01:59 PDT

Hello,

Looks like something has caused your mappings to be interpreted as a unidirectional 1:M instead of bi-directional. A unidirectional 1:M is similar to a M:M in that it requires a relation table, which would default in this case to be the TESTPARENT_TESTCHILD table.

You will need to check the mappings on the TESTCHILD object, and verify that there are no warning messages on deployment that are being missed involving the Testchild->TestParent mapping or its ID field. The TopLink essentials version shipped with OC4J 10.1.3.1 was a much older build than the one shipped with 10.1.3.3, and there have been quite a few validation changes made during this time.

Can you post the 1:1 mapping and how you have defined the primary key on the TestChild object?

Best Regards,
Chris
[Message sent by forum member 'chris_delahunt' (chris_delahunt)]

http://forums.java.net/jive/thread.jspa?messageID=238451