OK, I just tried with the castle dynamic proxies (before i had LinFu)
AND IT WORKS!! This means, that it is a problem with LinFu proxies!
The proxy did load the values, but they are not accessible by the non-
public members. NH seems to create two instances of the entity, one
that is derived from the entity, and one which is a genuine entity
which holds the values. When entering the entity by an non-public
member, you are not "forwarded" to the other instance which holds the
values. This is what I found out using the debugger.
Private setters (usually) work well without field access. It is mapped
"normally":
<property name="PrivateSetter "/>
That's it.
As far as I can tell, internal members don't work with LinFu.
On 24 Mrz., 13:32, Nexus <[email protected]> wrote:
> Hi,
>
> Without questioning the implementation ;), it has nothing to do with
> proxying as the proxy should have loaded all values as a result from
>
> "Assert.AreEqual("A", obj.PrivateSetter) "
>
> Or is it caused by the private set {} itself ?? (What is the mapping
> here nosetter.camelcase ???), could be that the proxy generated by
> only having a public getter does not shadow a setter (because you
> didn't ask him !!), advise if you use nosetter.camelcase use your
> field directly or let the proxy have a protected set instead of a
> private one.
>
> Hope that it explains a little :S
>
> Regards
--
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.
