Hi Abe, I got a chuckle out of your solution, which, in a long tradition of good engineering, changes the problem.
Unfortunately, customers are not always open to suggestions about how their requirements can be modified. So, I've changed the bug report to a feature request, as it appears the issue is a limitation rather than a bug. Thanks, David Abe White wrote: >> It's possible that I'm stumbling around in the dark. If so, it >> would be >> great if you could shine a light on the issue. > > Just make it a two-sided relation, as is required by standard JPA. > Problem solved. > > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual or > entity named in this message. If you are not the intended recipient, and have > received this message in error, please immediately return this by email and > then delete it. > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
