There are cases where one needs to set a default for an entity's property, prior to the entity being inserted, but not when the entity is first constructed.
The a pre-insert event-listener would seem to be the proper place to do this, but there seems to be a problem with doing this if the event causes lazy loads to occur. We risk getting an error such as "collection xxx was not processed by flush()". This error can occur quite subtly and popup infrequently, depending on factors such as caching. I can't think of another way of replicating this behaviour. Any ideas? -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to nhus...@googlegroups.com. To unsubscribe from this group, send email to nhusers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
