Hi Kent, would you mind sending me a small test case that demonstrates what you're experiencing. If it's a bug, it makes it much easier to track down.
RIFE should fetch the related MOSecondBean for each new instance of MOFirstBean. Are you sure you have a list of different instances? If that doesn't work, setting the property that returns the MOSecondBean to null, should aftewards re-fetch it when you use the getter. Best regards, Geert On 12 Aug 2007, at 12:07, Coat wrote: > > Hello all, > > I have a many to one relationship setup just like MOFirstBean and > MOSecondBean in the rife unittests > (TestGenericQueryManagerManyToOne.java). When I am looping through a > List of MOFirstBeans, it appears it only loads the MOSecondBean from > the first MOFirstBean in the List, when actually the all the > MOFirstBeans point to different MOSecondBeans. > > However, when looking at the actual database, it does look like > everything is correct and pointing to the correct identifiers setup in > the MetaData for each of these beans. > > In debugging it looks like this may be related to the lazy loading of > the MOSecondBean, but I'm not sure. Do I need to do something to > assure that the correct relationship is being pulled from the > database? > > Thanks! > Kent > > > > -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rife-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rife-users?hl=en -~----------~----~----~----~------~----~------~--~---
