[
https://issues.apache.org/jira/browse/OPENJPA-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119685#comment-18119685
]
ASF subversion and git services commented on OPENJPA-2991:
----------------------------------------------------------
Commit 560121f926953acb178a963fb0cf644a1ac4bcb0 in openjpa's branch
refs/heads/OPENJPA-2991 from Richard Zowalla
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=560121f92 ]
[OPENJPA-2991] Gate the nested compound selection rejection behind a
compatibility option
Rejecting nested tuple/array selections in CriteriaBuilder.tuple()/array()
drops an OpenJPA extension that applications may rely on. Keep the
specification behaviour as default and add the compatibility option
AllowNestedCompoundSelection to restore the historic nesting support.
> Deeply nested multiselect extension now rejected
> ------------------------------------------------
>
> Key: OPENJPA-2991
> URL: https://issues.apache.org/jira/browse/OPENJPA-2991
> Project: OpenJPA
> Issue Type: Sub-task
> Components: jpa
> Affects Versions: 4.2.0
> Reporter: Maxim Solodovnik
> Priority: Major
> Fix For: 4.2.0
>
>
> Discussion thread:
> https://github.com/apache/openjpa/pull/144#discussion_r3683006744
> **(medium)** testDeeplyNestedShape previously verified OpenJPA's documented
> extension supporting arbitrary nesting of tuple/array selections (the old
> comment even said the negative test was retired for that reason); it is now
> inverted to expect IllegalArgumentException. The spec's "must not" has been
> there since 2.0, so this drops a working extension existing applications may
> rely on. Intentional, and should it be release-noted?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
