Indeed I am! Stay tuned :)

On Thu, Feb 5, 2009 at 8:47 AM, James Gregory <jagregory....@gmail.com>wrote:

> You get that exception when then ordering is incorrect in the XML, this
> sounds like a bug.
> The idea of a model between the mapping and XML is one we're already in the
> process of tackling, Paul Batum is working feverishly at it.
>
>
> On Wed, Feb 4, 2009 at 9:26 PM, mcintyre321 <mcintyre...@gmail.com> wrote:
>
>>
>> I've just had an error while trying to automap some inheritance. "The
>> element 'class' in namespace 'urn:nhibernate-mapping-2.2' has invalid
>> child element 'joined-subclass'"
>>
>> I may be barking slightly up the wrong tree about how the guts of
>> FluentNH work, but it looks to me like FNH builds up a virtual xml
>> mapping file, then parses it. I have a suggestion to make this easier.
>> A while back I did some experiments with generating a statically typed
>> object model for the Linq To Sql XSD schema using the alpha 0.2
>> release of Linq to XSD. If you were to generate a class model based on
>> the NHibernate XSD schema you might find manipulating the virtual
>> mapping file a lot easier - for example, it wouldn't be possible to
>> add invalid elements to a particular node. I've generated one of these
>> models for NH before using Linq To XSD when I was thinking about
>> making a similar tool to FNH, but I stopped experimenting on it when
>> FNH came along.
>>
>> Oh I've just had a look at the source it looks like its already been
>> done manually... Basically you can generate a load of the stuff in
>> the .Mapping namespace
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to