Hi Don, Thanks that solved the problem. Without your solution I would have been stuck.
I am still surprised the NHibernate does not solve this pattern as elegantly as what I come to know learn about it. (E.g. many-to-many boilerplate, sub classing and so on). Especially on a rather common scenario such as this. It meant that I had to add properties to my domain class (ValueItem) which I don't need require in my domain logic. This meant I also had to set these newly introduced myself :(. I still believe this should be possible as all the information is available in the mapping layer. Either possible in a future version or perhaps solve it in a different way. Kind regards, Philip On Mar 26, 6:34 am, Philip Fourie <[email protected]> wrote: > Thanks Don. This seems exactly what I need. Let me try it and I will > report back. -- 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.
