A usage similar to .ForTypesThatDeriveFrom(map =>
map.Component()) would definitely be optimal since my
component objects would be 1:1 mappings, but for derivations off that
I assume it'd have to be almost the same as normal mapping unless you
add convention support specifically to that component.
Hi Chris
Basically we will attempt to automap what we can from your class, however
after that point you can
override our settings with your own in that center bit.
How does that sound?
Andy
On Wed, Dec 10, 2008 at 4:07 PM, Chris Marisic <[EMAIL PROTECTED]>wrote:
>
> What exactly goes in ".WithC
What exactly goes in ".WithComponent( m => // Some mapping
logic here)" is what I don't understand.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email to fluen
Hi Chris
That is currently the only way to map components using Auto Mapping, we
really need to look into a better way of doing this but I'm currently
working on inheritance support which is complex, once that's done component
mapping is on my to-do list. However we're
always grateful to receive pa
