[
https://issues.apache.org/jira/browse/OPENJPA-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-2420.
--------------------------------------
Resolution: Fixed
Already fixed on master: FetchConfigurationImpl.resetFetchGroups:472-477 calls
clearFetchGroups(list empty) so 'default' comes back only when no list is
configured, then adds the configured groups (ee6f4acc3, ancestor of HEAD);
FetchPlanImpl.resetFetchGroups delegates to it. Closing; please reopen if this
still happens with OpenJPA 4.x.
> FetchPlan.resetFetchGroups() restores "default" FetchGroup even if omitted
> from "openjpa.FetchGroups" property
> --------------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-2420
> URL: https://issues.apache.org/jira/browse/OPENJPA-2420
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Reporter: Jody Grassel
> Assignee: Jody Grassel
> Priority: Minor
>
> The method FetchPlan.resetFetchGroups() restores and activates the "default"
> fetch group whether or not it is listed by the "openjpa.FetchGroups" property
> when that property is used.
> When an EntityManager is created by a persistence unit definition utilizing
> "openjpa.FetchGroups" that omitted including "default" in its value, that
> EntityManager's initial FetchPlan honors the omission. However, calling
> FetchPlan.resetFetchGroups() includes enabling "default" causing the reset
> FetchPlan to not be equivalent to the initial default FetchPlan.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
