[
http://issues.apache.org/jira/browse/OPENJPA-40?page=comments#action_12433878 ]
Thomas Risberg commented on OPENJPA-40:
---
I made the changes you suggested and I can now run the test relying only on
annotations. As soon as I involve an
metadata-complete element in orm.xml is ignored
---
Key: OPENJPA-44
URL: http://issues.apache.org/jira/browse/OPENJPA-44
Project: OpenJPA
Issue Type: Bug
Components: jpa
[
http://issues.apache.org/jira/browse/OPENJPA-42?page=comments#action_12434017 ]
Marc Prud'hommeaux commented on OPENJPA-42:
---
Hmm ... the ClassCircularityError should have been resolved by my fix for
OPENJPA-40. Can you make sure you
[ http://issues.apache.org/jira/browse/OPENJPA-39?page=all ]
Abe White resolved OPENJPA-39.
--
Resolution: Won't Fix
Turns out the problem is more complicated than just having a foreign key. The
issue is:
- OpenJPA's UpdateManager plugin does not reorder
Hi Abe,
- When you delete a parent object and the operation cascades to
children, the object-level operation order is delete parent, then
delete children.
In my experience, the cascade should delete the children first. This
solves 99% of the cascade delete issues.
Craig
On Sep 11,
[ http://issues.apache.org/jira/browse/OPENJPA-42?page=all ]
Thomas Risberg updated OPENJPA-42:
--
Attachment: OPENJPA-42.zip
Marc,
I saw your fix for the circular reference and I don't see the error message
right now after checking out the latest (now
[
http://issues.apache.org/jira/browse/OPENJPA-42?page=comments#action_12434042 ]
Marc Prud'hommeaux commented on OPENJPA-42:
---
I'm surprised by the build error ... I haven't seen it before. However, I agree
that it sounds like the
