[
https://issues.apache.org/jira/browse/OPENJPA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132026#comment-18132026
]
ASF subversion and git services commented on OPENJPA-2940:
----------------------------------------------------------
Commit f77551bd60e6cf358052b065893b057dff3ebf8f in openjpa's branch
refs/heads/OPENJPA-3021 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=f77551bd6 ]
[OPENJPA-3024] Keep orphan removal on a relation that also cascades remove
(#224)
* [OPENJPA-3019] test for orphanRemoval case failing for Apache OpenMeetings
* Removal test is improved
* [OPENJPA-3024] Keep orphan removal on a relation that also cascades remove
Since OPENJPA-2940 the annotation parser applied cascade=REMOVE/ALL after
orphanRemoval, so the immediate cascade replaced the dependent marking and
an element removed from such a collection was no longer deleted. Apply
orphanRemoval last again and remove a dependent value together with its
owner, as the specification requires for orphanRemoval.
---------
Co-authored-by: Maxim Solodovnik <[email protected]>
> Implement Jakarta Persistence 3.2
> ---------------------------------
>
> Key: OPENJPA-2940
> URL: https://issues.apache.org/jira/browse/OPENJPA-2940
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Paulo Cristovão de Araújo Silva Filho
> Assignee: Maxim Solodovnik
> Priority: Major
> Fix For: 4.2.0
>
> Attachments: image-2026-03-28-14-55-26-463.png
>
>
> Implement Jakarta Persistence API 3.2 as prescribed by
> [specification|https://jakarta.ee/specifications/persistence/3.2/] and
> required by Jakarta EE 11.
> This change requires JDK17 or higher compatibility and needs considerable
> checks.
> I've already pushed a branch (WIP) without the proper API bump, focusing on
> updating dependencies while keeping the project passing its current tests at
> least in default profile.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
