I did read it, but that's not my point. I'm doing a projection of an existing entity to a light-weight DTO. The AliasToBean transformer requires me to provide a default _public_ parameterless constructor to work with it, the reason for that being it's using Activator.CreateInstance(type) instead of Activator.CreateInstance (type, true).
I'm perfectly aware that I can implement my own transformer or tupelizer, however the problem is the behavior of AliasToBean. AFAIK AliasToBean is using setters on the instance, ideally making the constructor irrelevant (besides the one for the activator). My point is simply this: Make AliasToBean accept non-public constructors. If I'm completely of-course, please let me know. BTW: I'm on the current NH trunk. On 12 Mar., 15:22, Fabio Maulo <[email protected]> wrote: > 2009/3/12 TigerShark <[email protected]> > > > > > Yeah I know, but still, it's kind of strange that the default > > AliasToBean transformer doesn't support other that strict public > > constructors. > > Actually I thought that one of the primary goals for NH was to provide > > transparent persistence with close to no restrictions on the domain > > model. Now I _have_ to provide a parameterless public constructor, > > even though it's never user by anything by NH... > > Please read the blog post.. > "If you are working with NH you know that NH likes POCOs and you must have a > default constructor without parameters. Starting from today that is the > past."... > > -- > 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 -~----------~----~----~----~------~----~------~--~---
