I have the following element in my mapping file:
<class name="Foo">
<map name="Bars" table="Bar" access="field.camelcase" >
Note the access is by field using camel case. In C#, my "Foo" class
contains a field named "bar", but there is no corresponding property.
This works fine in a previous version of NH and seems to be in accord
with the documentation.
However, using NH3.1, I get a PropertyNotFoundException in
NHibernate.Properties.FieldAccessor.cs. The GetGetter function has the
following comment: "it is a field access that imply the existence of
the property".
This seems like a pretty major change. Why should a field access imply
the existence of the corresponding property?
-- Brian
--
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.
