Please try in a realistic setup if the fix works. I just ran a version of your test to verify the fix.
The fix (or the error) has nothing to do with FetchPlan -- it is some other internal optimization that caused the AOOB exception. Daryl Stultz wrote: > > On Fri, Dec 11, 2009 at 3:31 PM, Pinaki Poddar <[email protected]> wrote: > >> >> Hi Daryl, >> The change is committed on trunk at revision 889799. >> Can you try to see if it resolves the problem? >> >> I got the latest as of this afternoon, a few past 889799. I've tested > against my isolated unit test and it's good. I'll try it in my full > application when I get a chance. > > I've pulled back from using fetch plan completely until this is resolved. > Can you give me some idea of the problem, perhaps I can use fetch plan > selectively knowing what the arrangement is that yields the error? > > Thanks for the quick attention! > > -- > Daryl Stultz > _____________________________________ > 6 Degrees Software and Consulting, Inc. > http://www.6degrees.com > mailto:[email protected] > > ----- Pinaki -- View this message in context: http://n2.nabble.com/Fetch-plan-question-tp4117231p4154130.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
