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