ah... and obviously you can implement your own accessor-strategy doing what you need.
On Sat, Mar 26, 2011 at 3:37 PM, Fabio Maulo <[email protected]> wrote: > If the class does not contains a property named "Bars" then the mapping > <map name="Bars"... > should trows an exception. > > If you don't have a property your mapping should be: > <map name="bar" access="field" ..... > > > On Sat, Mar 26, 2011 at 3:33 PM, Brian Berns <[email protected]> wrote: > >> Also, the ReflectHelper.HasProperty has the following comment: >> >> When the user defines a field.xxxxx access strategy should be >> because both the property and the field exists. >> NHibernate can work even when the property does not exist but in >> this case the user should use the appropiate accessor. >> >> If field.xxxxx does not work, what is the "appropriate accessor" in >> this case? >> >> -- >> 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. >> >> > > > -- > Fabio Maulo > > -- Fabio Maulo -- 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.
