I apologize I didn't elaborate further ;) . I meant to move the initializers to a non-default constructor. I've had horrible issues in the past with initialization in the default constructor overwriting the proxying that NHibernate does whenever it retrieves the class back from the database. The issue wouldn't have cropped up until after Carmine had been able to successfully save the object graph back though, which seems to have been the problem in the first place. Good catch on the save Paul, looks like that fixes the issue :)
On Tue, Oct 6, 2009 at 7:09 AM, CarmineM <carmine.mol...@gmail.com> wrote: > > Hi Paul, > > Thank you so much for your effort and huge pointers. > I'll give it a try as soon as I get home. > > I also have a doubt about the repository implementation. > > First off, I'll remove the confusion on the mappings. > > About the repository call to persist the objects, (as of now) it just > calls the > session's save method on the item passed. > I don't use transactions, yet. > > Thanks again for your help. Will let you all know about the epilogue. > > > > -- - Hudson http://www.bestguesstheory.com http://twitter.com/HudsonAkridge --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibernate@googlegroups.com To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
