Hi Kevin,
Thanks for the response. Here some answers:
1. Why is the @InverseLogical annotation required?
I included this quite early in the development of as the manual suggested that
using the annotation would cause openJpa to manage the relations for me.
Are you implying that mappedBy in
Hi John,
1. The @InverseLogical annotation shouldn't affect your scenario. I was
just curious as to why you were using it. My ignorance of the usefulness
of this property would shy me away from its usage, but that's just me.
2. Thanks for the explanation of your update() method. This sounds
Excellent. Good to hear. Good way to end my week... :-)
Kevin
On Thu, Jun 7, 2012 at 10:08 PM, manushka padk...@gmail.com wrote:
Kevin,
You are right, my bad, there was a mistake in the way I first wrote the
relationship.
Yes, the crefernceColumnName works, we are using openjpa 2
- Anu
John -
It's Friday afternoon, so I haven't really dug into this issue deeply, but
for giggles can you try to set openjpa.InverseManager to false? I struggled
to recreate your failure, but as soon as I set that property to true I
started seeing the same behavior.
Thanks,
Rick
On Fri, Jun 8, 2012
