You should check if the collection was initialized or not.Where was not initialized it does not have change. btw, in general, you can avoid to check the collection it self because each collection element will be catch during cascade.
2009/4/17 Marc Climent <[email protected]> > > Hi, > > I've been struggling with a problem and reading the group I found the > source of the problem here: > > http://groups.google.es/group/nhusers/browse_thread/thread/897f808d7deaf281/16389904749580fe > > I was accessing a lazy collection in the event that was not yet > persisted and got a "collection not processed > by Flush". > > I have a method that checks the changes between the oldState and the > newState and I've added a condition to check if the objects are > INHibernateProxy. In that case, I don't check their values so I don't > risk to access a modified but unflushed collection. > > For the moment is ok, but is there any strategy to delay the process > until the data is flushed? How can I access the lazy loaded > collections within an Update event without causing the exception? > > Thanks. > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
