internal virtual can't be intercepted.If you want you can simply turn off de
proxy validator and manage any kind of surprise by yourself.
<property name="use_proxy_validator">false</property>

2009/9/27 Brendan Kowitz <brendan.kow...@gmail.com>

>
> Hi,
>
> Can someone please help me understand the following:
>
> In the previous version of NH (2.0.1) the following property will
> validate and is compatible with the Castle Proxies:
>
> internal virtual BusinessObject Parent
> {
>  get { /*code*/ }
> }
>
> However, in 2.1 it errors saying that the types should be virtual
> 'public/protected' or 'protected internal'.
> I have issues with this because marking a property with 'protected
> internal' exposes the property to inherited types in OTHER assemblies
> (effectively protected OR internal). Given that this was never a
> requirement before, it feels like a bit of a bad requirement to impose
> now.
>
> Can someone please explain why this requirement is now there and what
> it is trying to enforce so I can at least understand what it is
> intending to achieve.
>
> If this restriction is not entirely needed, and I am 100% certain
> these types of properties will NEVER map to DB properties I am
> intending to create my own Mashup ByteCode provider using the Castle
> proxy factory and the Type Validator from 2.0.1.
>
> Thanks,
> Brendan
> >
>


-- 
Fabio Maulo

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to nhusers@googlegroups.com
To unsubscribe from this group, send email to 
nhusers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to