Correct; the generated HBM files have no whitespace... easy enough to
fix with a ctl+k, ctl+d in VS. ;)
On May 1, 11:41 am, James Gregory <jagregory....@gmail.com> wrote:
> Ah yes, silly mistake. I've added this in my local copy, but am in the
> middle of some changes so haven't yet committed it. I've also noticed that
> dynamic-component and one-to-one are both missing too, so there may be more
> too. This should really be reviewed.
> As for the other thing, is it that there's no whitespace in the output?
>
> On Fri, May 1, 2009 at 5:33 PM, Stuart Childs <chil...@gmail.com> wrote:
>
> > In my case, it looks like it was because the sorting dictionary in
> > SortChildren() in XmlHibernateMappingWriter.cs was missing a
> > "component" pair. Adding
> > { "component", new SortValue { Position = PartPosition.Anywhere, Level
> > = 2 } },
> > seems to have fixed my issue with that class, but it's hard to say if
> > this is a complete fix. It does appear that all elements are grouped
> > together in all of my mapping files with that change.
>
> > I'd submit a patch (and will if it's helpful to you for tracking
> > purposes) but it seems like a pretty trivial change and if one tag was
> > missing from the sorting dictionary, it may be worth double checking
> > that all possible types are there.
>
> > On May 1, 11:09 am, James Gregory <jagregory....@gmail.com> wrote:
> > > Stuart: It might be too late now, but we'd greatly appreciate seeing the
> > > mappings causing the problems for you. They'd help us debug the ordering
> > > code.
>
> > > On Fri, May 1, 2009 at 5:05 PM, Stuart Childs <chil...@gmail.com> wrote:
>
> > > > While I'm not using AutoMappings, I was having a similar issue but was
> > > > more severe (with only one of my classes, too... one of many oddities)
> > > > where properties/components were being put before the <id> tag,
> > > > causing NHibernate to fail. It's very bizarre, but grouping all the
> > > > Map(), Component(), and References() calls separately and playing with
> > > > the ordering of the calls within those groups finally spit out a
> > > > mapping that passes validation... maybe you can try a similar
> > > > workaround until the issue is fixed? (I'm assuming it's a result of
> > > > the hacking they've been doing on the code to get the new model in)
>
> > > > On May 1, 10:56 am, MaggiePlusPlus <maggielongsh...@gmail.com> wrote:
> > > > > I updated to version 464 of FNH and the columns are again out of
> > order
> > > > > and the hbm.xml files have no formatting - all on one line.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
