A usage similar to .ForTypesThatDeriveFrom<Person>(map => map.Component<Address>()) 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.
On Dec 11, 11:35 am, "Andrew Stewart" <andrew.stew...@i-nnovate.net> wrote: > 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 > <chrismari...@hotmail.com>wrote: > > > > > What exactly goes in ".WithComponent<Address>( m => // Some mapping > > logic here)" is what I don't understand. > > -- > ================= > I-nnovate Software - Bespoke Software Development, uk > wirral.http://www.i-nnovate.net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibernate@googlegroups.com To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
