Schema validation is the only expensive part of using XML, but as Hudson already pointed out it's a one-off operation. Unless you have a *massive* domain model, then you're not going to feel it. We are going to move away from XML, but it won't be until after 1.0; however, we may implement the ability to merge the XML into one large document before passing to NH, this has been proven to reduce the validation time considerably.
Unless you are feeling the pain, I wouldn't be concerned about it. On Thu, Jul 16, 2009 at 8:02 PM, Mikael Henriksson <[email protected]>wrote: > I don't want to be rude but I doubt the xml mappings could possible cause > any real performance issues. > > 2009/7/16 Hudson Akridge <[email protected]> > > Not to second guess your setup, but loading mapping files, xml or >> otherwise, should typically only happen only once in your application >> lifecycle, usually at startup. If you're generating NHibernateConfiguration >> objects frequently, then whether or not it's using XML as an intermediary >> will be the *least* of your performance woes. >> >> On Thu, Jul 16, 2009 at 1:33 PM, Eb <[email protected]> wrote: >> >>> >>> I was hoping to bypass the use of mapping xml for performance >>> reasons. I assumed Fluent NHibernate did this. >>> >>> >> >> >> -- >> - Hudson >> http://www.bestguesstheory.com >> http://twitter.com/HudsonAkridge >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
