Thanks for the quick reply.
I tried that but with no luck.
I did something like this before executing the query:
OpenJPAEntityManager ojem = OpenJPAPersistence.cast(entityManager);
System.out.println("getMaxFetchDepth() before: " +
ojem.getFetchPlan().getMaxFetchDepth());
ojem.getFetchPlan().setMaxFetchDepth(15);
System.out.println("getMaxFetchDepth() after: " +
ojem.getFetchPlan().getMaxFetchDepth());
ojem.getFetchPlan().addFetchGroups("State_OutgoingTransitions",
"IncomingTransitions");
The output is:
getMaxFetchDepth() before: -1
getMaxFetchDepth() after: 15
The result is the same as described in the first post.
Am i doing it wrong?
Pinaki Poddar wrote:
>
> Hi,
> There are two attributes that control the closure of a graph as fetched by
> a FetchPlan/FetchConfiguration, namely
> Recursion Depth
> Max Fetch Depth
>
> According to the cited use case, Max Fetch Depth is the relevant attribute
> that will control depth of traversal from a root entity (s1). By default,
> the max fetch depth is set to 1 and hence the immediate neighbors of s1
> are fetched and not s4 or s5 which is at depth 2 from s1.
>
> Recursion depth, on the other hand, controls the depth of traversal for
> recursive relation on types. If s1 had a recursive relation then recursion
> depth would have controlled traversal of that relation path.
>
>
--
View this message in context:
http://n2.nabble.com/Fetchgroups-recursion-problem-tp3874382p3877617.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
