Hello, Thanks Geert! Let me know if you need any help.
Kent On Aug 18, 5:28 pm, Geert Bevin <[EMAIL PROTECTED]> wrote: > Hi, > > sorry for the delay, you caught me right when I was going to San > Francisco and returning in the same week, very busy time. This > effectively seems to be a bug. I don't seem to qualify the lazy > loading query with the identifier of the firstbean. I'll look into > fixing the bug tomorrow. > > Thanks for the useful bug report. > > Take care, > > Geert > > On 13 Aug 2007, at 06:11, Coat wrote: > > > > > > > Hello, > > > I created a quick test case using RIFE/Jumpstart so you or anyone > > could take a look if you don't mind. Download it here: > >http://starlingmarketing.com/motest.zip Just run it and go to > > localhost:8080/motest. The relevant stuff is in elements/ > > MOTest.java. If you go to localhost:8080/crud you can see that the > > everything is getting saved in the database correctly (and you can use > > the derby command line tools to view the actual data in the tables; > > the foreign keys match what they are supposed to be). > > > Anyway, localhost:8080/motest shows that only the first MOSecondBean > > is getting loaded. I'm not 100% sure when or how in the for loop to > > call setSecondBean(null), but I suspect that is probably the answer, > > but I am kind of a novice :) > > > I'm probably missing something simple as usual... > > > Thanks! > > Kent > > > On Aug 12, 4:44 pm, Geert Bevin <[EMAIL PROTECTED]> wrote: > >> 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 > > -- > 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 -~----------~----~----~----~------~----~------~--~---
