|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I incorrectly marked this issue as applicable to 3.0.0.Alpha. The actual version tested was 4.0.0-SNAPSHOT. I've yet to find a way that I can modify the version, and more importantly raise the priority, which seems a bit higher than documentation and utility tasks.
The find/getReference methods cannot be expected to retrieve the correct subtype if the persister does not inquire beyond the type passed as a parameter. I've tried modifying (not committed nor pull-requested) the tested entities to include @Table (in non-single table this should be the default?), but the hint does not seem to be respected. JPA 2.0 Spec - section 2.13 Naming of Database Objects indicates the same in my interpretation.