Nhibernate: Get real entity class instead of proxied class

Question

Is there a way to make nhibernate return my class instead of its proxy class? I dont mind if it's not lazy or cant be updated.

score 12 · Accepted Answer · answered Mar 28 '11 at 06:34

12

You can unproxy class with this code

session.PersistenceContext.Unproxy(proxiedInstance)

answered Mar 28 '11 at 06:34

Sly

15,046
12
60
89

12

Is there a way to unproxy all associations as well? It unproxies my main object but its relations to other object keep proxied. – ryudice Mar 28 '11 at 20:43

score 2 · Answer 2 · answered Mar 22 '17 at 03:24

You can use following code to get real object

InstanceType instance;
if (proxiedInstance is INHibernateProxy)
{
 var lazyInitialiser = ((INHibernateProxy)proxiedInstance).HibernateLazyInitializer;
 instance = (InstanceType)lazyInitialiser.GetImplementation();
}

score 2 · Answer 3 · answered Mar 28 '11 at 07:14

2

You should define this in your mapping, by defining lazy="false"

<class name="MyEntity" table="MyTable" lazy="false">
</class>

answered Mar 28 '11 at 07:14

Frederik Gheysels

56,135
11
101
154

score 0 · Answer 4 · answered Mar 28 '11 at 05:15

0

I'm using AutoMapper to achieve something similar in Entity Framework.

var nonProxiedInstance = Mapper.DynamicMap<YourType>(proxiedInstance);

That would work if you do not have navigation properties. Otherwise, you'll need to configure a mapping to ignore those properties.

Note: This is (obviously) an inefficient solution.

answered Mar 28 '11 at 05:15

Ed Chapel

6,842
3
30
44

2

This doesn't work. The proxy doesn't contain the properties of the inherited (real) class, so it would be missing in the mapped type as well. – Stefan Steinegger Mar 28 '11 at 08:12

score 0 · Answer 5 · answered Mar 29 '11 at 00:16

0

You can use the technique described in http://sessionfactory.blogspot.com/2010/08/hacking-lazy-loaded-inheritance.html (you'll need to do it recursively)

answered Mar 29 '11 at 00:16

Diego Mijelshon

52,548
16
116
154

CSharpBender · Answer 6 · 2021-05-28T05:53:19.257

0

session.PersistenceContext.Unproxy(proxiedInstance) will not unproxy the associations. Also the no-proxy lazy loading does the same thing. Disabling lazy loading is not a good idea and AutoMapper would navigate all the properties and trigger the loading mechanism.

IUnitOfWork.Unproxy from the NHUnit package could be used to unproxy the object and it's relations. This method will not initialize any proxy objects by mistake.

edited May 28 '21 at 05:53

answered Feb 08 '21 at 13:36

CSharpBender

21
2

What specifically is "none of the above"? That comment doesn't work when people submit in new answers. You should specify what techniques won't work and why. – Shiv May 27 '21 at 00:00

Nhibernate: Get real entity class instead of proxied class

6 Answers6

Linked