Yes, I knew about <typedef> but was more looking for a way to skip the type from the <property> all together.
We're now in a situation where we want to change an old usertype to a new one. This usertype is used in many places and it would have been nice to declare this NH type <-> .net type on one central place instead of having it spread out in many different mapping files. Thanks for your feedback though. At least I now know that I don't have to search for it any longer ;) /Roger From: [email protected] [mailto:[email protected]] On Behalf Of Fabio Maulo Sent: den 2 april 2009 15:50 To: [email protected] Subject: [nhusers] Re: Default IUserType/ICompositeUserType for certain type <typedef> is for short. We can implement something more to use <typedef> even when you don't specify the type in a property. 2009/4/2 Roger Kratz <[email protected]<mailto:[email protected]>> Hi Let's say I have <property name="MappedX" type="MyUserTypeForX" > [...] In my case every time a type X is mapped, I want my IUserType/ICompositeUserType MyUserTypeForX to be used. Can I somewhere tell NH this instead of explicitly repeat this in the mapping files? Of course this is no big deal, but it would be nice to do this on dialect (or configuration or some global mapping?) level. Maybe I can already but I just don't know how? Thanks in advance Roger -- 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 -~----------~----~----~----~------~----~------~--~---
