This will all be fixed for our imminent 1.0 release.
On Mon, Aug 3, 2009 at 10:11 PM, unacoder <[email protected]> wrote:
>
> i have not been able to find a way to map a component hierarchy. is it
> even possible?
>
> since I haven't been able to map these classes the way i want, i've
> turned them into full-blown entities, but i'm finding that i can't
> write the mapping code the way i want, so this next bit might be a
> feature request.
>
> i've currently got a small-ish block similar to
>
> DiscriminateSubClassesOnColumn<string>("TYPE")
> .SubClass<TypeA>("TypeA", x => { })
> ....
>
> i'd like to be able to be able to put the SubClass calls in a loop to
> ease maintenance while we add more and more subclasses, all of which
> will be found using reflection. the problem i'm having with this
> approach is that the generic method calls are much more difficult to
> invoke using runtime type semantics. can we see an addition to the API
> to support the following (or anything better)?
>
> var subclasses = ...
> var part = DiscriminateSubClassesOnColumn<string>("TYPE");
> subclasses.ForEach(subclass => part.SubClass
> (subclass, ..., ...));
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" 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/fluent-nhibernate?hl=en
-~----------~----~----~----~------~----~------~--~---
