openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henno Vermeulen <he...@huizemolenaar.nl>
Subject RE: FetchPlan/FetchGroup behaviour
Date Thu, 04 Apr 2013 15:16:10 GMT
We also extensively use fetchgroups with the setting
	<property name="openjpa.DetachState" value="fetch-groups(DetachedStateField=false)"/>
and I never experienced such a problem.

Are you 100% sure that you have instantiated and populated the list before saving? (We always
initialize each list to an empty ArrayList, not sure if that could be it.)

Could you try using DetachedStateField=false? We did have a few issues when using DetachedStateField=true.
From our issue tracker I can see that we had a failing test where a transaction saw stale
data in the list when objects in the list were updated in a different earlier transaction.


Additionally we use the option <property name="openjpa.AutoDetach" value="commit" />,
not sure if this matters.

Good luck,
Henno


-----Oorspronkelijk bericht-----
Van: Guillaume Chauvet [mailto:guillaume.chauvet@qualiformed.com] 
Verzonden: donderdag 4 april 2013 16:48
Aan: users@openjpa.apache.org
Onderwerp: Re: FetchPlan/FetchGroup behaviour

I've found an old unanswered ticket on the JIRA who described the same
behaviour [1]...
[1] OPENJPA-1030 <https://issues.apache.org/jira/browse/OPENJPA-1030>  



--
View this message in context: http://openjpa.208410.n2.nabble.com/FetchPlan-FetchGroup-behaviour-tp7583329p7583360.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Mime
View raw message