[
https://issues.apache.org/jira/browse/OPENJPA-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18120110#comment-18120110
]
ASF subversion and git services commented on OPENJPA-2991:
----------------------------------------------------------
Commit 393a48cc6f6f9bd03beaf1873b4b53eba94a6994 in openjpa's branch
refs/heads/master from Paulo Cristovão de Araújo Silva Filho
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=393a48cc6 ]
Merge pull request #195 from apache/OPENJPA-2991
[OPENJPA-2991] Gate the nested compound selection rejection behind a
compatibility option
> 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)
