the next thing to figure out is when the proxy code is triggered. if it's triggered when you call entity.parent.id then a session closed exception makes sense, if it's created when the root entity is hydrated then i'm at a loss.
however with all the time invested in this thread. I would either access the property within the session scope before closing the session, or eager load the parent entity to resolve the issue. In either case it doesn't work the way you expect/want it to. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/OjqNGH7UO_MJ. 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.
