Ignore public/internal fields for NHibernate proxy

问题

I have some entity types that I would like to lazy load. However, they have some internal (assembly) fields they expose, but are not used outside that class. These fields are compiler generated (F#) and I cannot change them. The an example exception is:

NHibernate.InvalidProxyTypeException: The following types may not be used as proxies: Mappings.MTest: field id@47 should not be public nor internal

I understand why NHibernate is doing this, and how having fields, if I accessed them, would mess up the lazy-loading properties of the proxies that are generated. However, since I know I won't be using the fields, can I override NHibernate somehow?

Is there any way I can say "ignore this field"? I'm using Fluent NHibernate, if that makes it easier.

Edit: I should also note, I'm using NHibernate 2.1.0 Alpha 2.

Edit2: The main gist here is that I want to keep LazyLoading enabled, which means I have to use the proxy generation. Disabling LazyLoading works (no proxies), but sorta defeats the purpose of a nice framework like NHibernate.

回答1:

I reassembled NHibernate (easier than getting the source and rebuilding) and removed the code that errors on internal/public fields. LazyLoading appears to work just fine without that check. (Although, I'm new to NHibernate and so there are probably scenarios I don't know about.)

Edit: Ah, there is a property, "use_proxy_validator" that will disable all validation checks. Good enough.

Fluently.Configure()
    .ExposeConfiguration(fun cfg -> 
        cfg.Properties.Add("use_proxy_validator", "false"))...

回答2:

Just set the lazy property to false,

 <class name="OrderLine" table="OrderLine" lazy="false" >

you can read more in: Must Everything Be Virtual With NHibernate? - http://davybrion.com/blog/2009/03/must-everything-be-virtual-with-nhibernate/

Ofir, www.TikalK.com

回答3:

You can use the

[XmlIgnore]

attribute to decorate the fields :)

回答4:

Can you use an Interface to declare the fields "used" ?http://nhibernate.info/doc/nh/en/index.html#persistent-classes-poco-sealed

"Another possibility is for the class to implement an interface that declares all public members"

I don't know if NH use the same @transient annotation/attribute as the JAVA version to ignore a property in persistent operations.

回答5:

You might want to take a look at this page which gives an overview of using F# with Fluent NHibernate.

Edit I just noticed your username. Am I correct in perhaps thinking that this is your blog? How foolish of me. It does seem to address your problem though, specifically "We start off by disabling LazyLoad because most of the properties are not virtual, and NHibernate will fail to validate the mapping. Instead, we explicitly LazyLoad things, like the Store reference."? Maybe I'm just misunderstanding the problem.

来源：https://stackoverflow.com/questions/741489/ignore-public-internal-fields-for-nhibernate-proxy