Hi, Thanks for replying.
I know the behavior when all of the properties of a component are null, then the component is null. That i'm sure off. But in the previous version NH2.1 I could alter that behavior abit using the propertys. I tell NH to map a field, with watever value is in the database, null or not. Then I access it using the property. The property then can check it if it is null or not. if it is null, I'll give a new object back. This behaviour now seems to me impossible. I map the field with access="field", and the property's logic to give me a new one back isn't accessed, it just gives me null. I map the field with access="property", and all is well I properably miss something here: why can't the proprety give me the value back of the field? Shouldn't it trigger the interceptor to invoke the real property? Thanks for some explanation... Kristof -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/WtP7WbneTCEJ. 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.
