Documentation says that you can specify access strategy specifically
<property
name="propertyName" (1)
column="column_name" (2)
type="typename" (3)
update="true|false" (4)
insert="true|false" (4)
formula="arbitrary SQL expression" (5)
access="field|property|ClassName" (6)
optimistic-lock="true|false" (7)
generated="never|insert|always" (8)
/>
On Fri, Nov 14, 2008 at 2:40 PM, Henning <[EMAIL PROTECTED]>wrote:
>
> Hi,
>
> I'm currently starting a new project using NH and I was wondering
> whether I should use field or property-access in my mappings.
>
> Especially I'm thinking about: when I use property-access I cannot
> mark properties as "readonly" (e.g. properties with no setter), field-
> access would offer me such a "protection". On the other side I won't
> be able to use auto-properties, so I would "trash" my code with
> mostly annoying backing-fields.
>
> So I thought I ask you guys, if there are any further considerations
> to take, and what access-method you mostly tend to.
> >
>
--
Tuna Toksöz
Typos included to enhance the readers attention!
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---
