Hi Michael,
Yes, the field inclusion in fetch group is determined by the field's name
with the declaring class and not by the defining class.
The recent commit 688777, adds the behavior you want. So
FetchPlan.addField(A.class, "b");
FetchPlan.addField(B.class, "code");
should fetch {A.b, A.b.code} but not {A.code}.
I have added a JIRA issue to track [1].
Let me know if you can try the recent changes and whether it addresses your
use case.
Regards --
[1] https://issues.apache.org/jira/browse/OPENJPA-704
[2]
http://n2.nabble.com/svn-commit%3A-r688777---in--openjpa-trunk-openjpa-kernel-src-main-java-org-apache-openjpa%3A-kernel-FetchConfigurationImpl.java-meta-FieldMetaData.java-tc781976.html
--
View this message in context:
http://n2.nabble.com/Fetch-Group-questions-tp534861p782029.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
