[
https://issues.apache.org/jira/browse/OPENJPA-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870490#action_12870490
]
Ravi P Palacherla commented on OPENJPA-1200:
--------------------------------------------
I agree that ElementClassCriteria is the easy solution for this issue, but what
is the purpose of having DiscriminatorColumn ?
Doesn't it mean Book entity is distinguished by discriminatory value BOOKS and
movie by MOVIES, meaning when artist .getBooks() is called then the
discriminatory value of books should only be considered ?
One more reason for working on this issue is because customer claims the use
case works on other JPA provides, TopLink, without the need for proprietary
annotations.
>From your previous notes, you are suggesting to revert the changes in this
>JIRA and use ElementClassCriteria as a solution.
Also from OPENJPA-1398, it does not look like my changes cover all the
scenarios properly.
So, I think the best thing to do here is to revert all the changes that went as
part of this JIRA and ask customer to use ElementClassCriteria.
Please confirm if my understanding is correct.
> Incorrect Entity is returned if ElementClassCriteria is not selected.
> ---------------------------------------------------------------------
>
> Key: OPENJPA-1200
> URL: https://issues.apache.org/jira/browse/OPENJPA-1200
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.0.0-M2
> Reporter: Ravi P Palacherla
> Assignee: Ravi P Palacherla
> Fix For: 1.1.1, 2.0.0-M3
>
> Attachments: openJPA-1200_1.1.x.patch, OPENJPA-1200_trunk.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
