The OP said:

"Declaring the property as virtual does work, but I don't
like it because virtual has semantic implications and so I can't
guarantee we could always use that approach. "

I believe he's looking for the not-mapped properties to not be marked
virtual. Unfortunately, due to how proxies work, you won't be able to
mix virtual with non-virtual as far as I know, unless you disable lazy
loading.

Here's an interesting read:
http://davybrion.com/blog/2009/03/must-everything-be-virtual-with-nhibernate/

On May 26, 6:06 am, Rory Plaire <[email protected]> wrote:
> Agreed. Don't map it. I have numerous properties not mapped and NH ignores
> them. What do you mean by "Simply not
> naming the column in the HBM.XML files isn't enough because NHibernate finds
> the Property by reflection"?
>
> On Wed, May 25, 2011 at 2:55 PM, Kim Johansson 
> <[email protected]>wrote:
>
>
>
>
>
>
>
> > Uhm... Don't map it.

-- 
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