Hello,

I am witnessing some unexpected behaviour with my many-to-one lazy-loading relationships.

The object that is being loaded by proxy has a base class with members that are also mapped.

ie:

class A
{
property AA
}

class B:A
{
property BA
}

and mapping

...
<property name="BA" column="ba"/>
<property name="AA" column="aa"/>
...


now when class B is loaded via proxy
<many-to-one name="B" column="bID"/>

only the property of class B is being loaded (BA), and not the property of class A (AA).

i only get this issue for single-ended proxies, the collection proxies seem to work fine.

if i set lazy=false for the many-to-one association, then the problem goes away, which makes me think it must be something to do with the proxy

if anyone has any ideas what is happening here it would be much appreciated

cheers,

matt

it seems like this was a problem around virtual members

class A had some none-virtual properties, but these were defined on an interface which class A implemented.

The seems to have had the result of nhibernate not complaining when it tried to create the proxy (as it would if the properties were defined on the object and not an interface), and instead just loading nulls for those non-virtual properties when objetcs were accessed by proxy.