More than a breaking-change it is part of a bug-fix related to not-set values when lazy-property is used. It includes an improvement because now you can use lazy-properties even when are not auto-properties.
On Wed, May 4, 2011 at 2:38 PM, Richard Birkby <[email protected]> wrote: > I don't remember seeing this breaking change in the release notes? > > Richard > > On 4 May 2011, at 14:54, Fabio Maulo <[email protected]> wrote: > > yes if you don't want use lazy-properties. > You can disable the validator but then you have to know what will happen if > you use lazy-properties. > > On Wed, May 4, 2011 at 10:39 AM, cremor < > <[email protected]>[email protected]>wrote: > >> I just tried a build of the current trunk (coming from 3.2.0.Alpha2) >> and was quite surprised that nothing worked any more because >> NHibernate complained about many of my entities not being proxyable. >> >> Example property: >> public virtual SomeEntity SomeEntity { get; private set; } >> >> Seems like in r5718 the DynProxyTypeValidator was changed to also >> check non-public property accessors (line 57 from >> "property.GetAccessors(false)" to "property.GetAccessors(true)"). I >> see that it's needed to check protected/protected internal accessors >> (so the previous code wasn't checking everything), but shouldn't >> private accessors be allowed? > > > > > -- > Fabio Maulo > > -- Fabio Maulo
