NHibernate 3.2 no longer uses the {Castle,Spring,LinFu} proxy providers,
instead, it uses it's own internal proxy provider. That explains why
removing it from your configuration does not change anything.
All methods and providers of your class must be now virtual, are you aware
of this change? Otherwise, you can set the following property on the
Configuration object:
cfg.SetProperty(NHibernate.Cfg.Environment.UseProxyValidator,
Boolean.FalseString);
RP
On Monday, July 30, 2012 10:26:02 AM UTC+1, sianabanana wrote:
>
> Hi
>
> In a previous project i have used nhibernate 3.1 and used the no-proxy
> function to stop child references being loaded as a proxy type.
>
> The proxy type is a pain when using inheritance and discriminator columns
> as you cant do a "is Class..." query on them.
>
> In a new project i am doing, i have added inheritance and needed to do
> this query so added the no proxy mapping.
> (im using fluent nhibernate and use .LazyLoad(Laziness.NoProxy) method in
> my mapping).
>
> As soon as this is added this method to the mapping i get a horrible
> "System.NotSupportedException: Specified method is not supported."
> exception.
>
> Im using the Castle proxy provider if that makes a difference. I tried
> removing this from my configuration but i still get the same error.
>
> Has something changed in 3.2 that i need to configure differently?
>
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/nhusers/-/tR1G0gSrgGYJ.
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.
