Ok, I was just surprised that it has changed so much between 1.2 and
2.0 ;)

On 18 mar, 10:27, Gustavo Ringel <[email protected]> wrote:
> There is no issue with the proxy, it just works this way. That's a dynamic
> proxy from Castle.
>
> Gustavo.
>
> On Wed, Mar 18, 2009 at 12:22 PM, graphicsxp <[email protected]>wrote:
>
>
>
> > Thanks, indeed my methods IsDeleted and IsChanged were not virtual and
> > I had to do this.
> > Any idea regarding the proxy thing ?
>
> > On 18 mar, 10:15, Gustavo Ringel <[email protected]> wrote:
> > > In NH 1.2 if you had somehing implementing an interface with a method
> > > IsDeleted, you didn't have to set it as virtual.
>
> > > From NH 2.0 also methods implementing an interface should be marked as
> > > virtual. I'm not sure why this was changed but i remember of having this
> > > problem.
>
> > > Gustavo.
>
> > > On Wed, Mar 18, 2009 at 11:43 AM, graphicsxp <[email protected]
> > >wrote:
>
> > > > Hello,
>
> > > > After changing my NHibernate dll from 1.2 to 2.0, I receive the
> > > > following errors when BuildSessionFactory() is called :
>
> > > > The following types may not be used as proxies:
> > > > DataTransfer.Cutting: method set_IsDeleted should be virtual
> > > > DataTransfer.MediaElement: method set_IsDeleted should be virtual
> > > > DataTransfer.Cutting: method set_IsChanged should be virtual
> > > > DataTransfer.MediaElement: method get_IsDeleted should be virtual
> > > > DataTransfer.MediaElementType: method set_IsChanged should be virtual
> > > > DataTransfer.Media: method AddMediaElement should be virtual
> > > > .
> > > > .
> > > > .
> > > > It goes on like that with all my Mapped entities.
>
> > > > What is going on ?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to