[
https://issues.apache.org/jira/browse/OPENJPA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539408
]
Kevin Sutter commented on OPENJPA-370:
--------------------------------------
Okay, my performance runs are not quite as drastic as the ones cited by
Patrick, but they still are not great. And, given the concerns about our
interpretation of the LoadFetchGroups processing (via the testcase analysis), I
will back out these changes from both the 1.0.x and 1.1.0 branches. I will do
this this afternoon.
Thanks for the insights and the patience while we figure this out. Teresa
should be back in the saddle next week and we can figure out the proper
solution and proper interpretation of LoadFetchGroups at that time (unless the
collective "we" can do it before she gets back).
Thanks,
Kevin
> LoadFetchGroup annotation was not recognized during the fetch1
> --------------------------------------------------------------
>
> Key: OPENJPA-370
> URL: https://issues.apache.org/jira/browse/OPENJPA-370
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.0.1, 1.1.0
> Reporter: Teresa Kan
> Assignee: Teresa Kan
> Fix For: 1.0.1, 1.1.0
>
> Attachments: OPENJPA_370_2.patch, TestFetchGroup.zip
>
>
> Employee class has a LoadFetchGroup annotation defined on the Rating field,
> when getRating was called, the address should be returned also. However,
> openjpa did not handle the LoadFetchGroup correctly, therefore, address was
> not eargly fetched.
> public class FGEmployee{
> @Id
> private int id;
>
> @OneToOne(fetch=FetchType.LAZY)
> private FGAddress address;
>
> @Basic(fetch=FetchType.LAZY)
> @LoadFetchGroup("AddressFetchGroup")
> private String rating;
>
> @ManyToOne(fetch=FetchType.LAZY)
> private FGManager manager;
> ..
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
