Before I get too far in finding a workaround, I want to check if there is any off the top answers to whether querying an entity with a lazy loaded many-to-one "no-proxy" property value in one session, closing that session, then calling SaveOrUpdate on the entity in another session is supported.
What appears to happen is that SaveOrUpdate attempts to load the lazy no-proxy property during the Update phase which leads to a LazyInitializationException since the update hasn't completed yet. Since I'm unfamiliar with this option and documentation appears sparse, I wanted to check if this is some misconfiguration or just unsupported. -r -- 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.
