> Is this fix complete in trunk? Yes. Does individual committer merges his/her changes or someone centrally does it?
Pinaki Poddar 972.834.2865 >-----Original Message----- >From: Michael Dick (JIRA) [mailto:[EMAIL PROTECTED] >Sent: Tuesday, September 18, 2007 3:01 PM >To: [email protected] >Subject: [jira] Commented: (OPENJPA-358) Recursion Depth for >Field f should be calculated w.r.t active fetch groups and not >all fetch groups > > > [ >https://issues.apache.org/jira/browse/OPENJPA-358?page=com.atla >ssian.jira.plugin.system.issuetabpanels:comment-tabpanel#action >_12528533 ] > >Michael Dick commented on OPENJPA-358: >-------------------------------------- > >Is this fix complete in trunk? If so we should probably get >the changes merged into 1.0.x. > >> Recursion Depth for Field f should be calculated w.r.t active fetch >> groups and not all fetch groups >> >---------------------------------------------------------------------- >> ----------------------------- >> >> Key: OPENJPA-358 >> URL: >https://issues.apache.org/jira/browse/OPENJPA-358 >> Project: OpenJPA >> Issue Type: Bug >> Affects Versions: 0.9.7, 1.0.0 >> Reporter: Pinaki Poddar >> Assignee: Pinaki Poddar >> Fix For: 1.0.1, 1.1.0 >> >> >> A field f can have multiple recursion depth specified under >different fetch groups. >> Give: >> f is a member of three fetch groups A,B and C with d1, d2, >d3 being its recursion depth in these groups respectively. >> Assertion: >> if A and B are active and C is inactive then effective >recursion depth of f should be max(d1,d2) and not max(d1,d2,d3). >> Currently recursion depth of f does not account for the >active groups and is computed over all the groups f is a member of. > >-- >This message is automatically generated by JIRA. >- >You can reply to this email to add a comment to the issue online. > > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
