Does it make sense to want a public property to access the mappings in a persistent model? I can imagine many uses for this:
* I want a DiagnosticMappingVisitor that does not need to write to a folder * I want to do some kind of post processing to the mappings * I want to build scaffolding (like rails style scaffolding) from the metadata in the model This should be very easy to do, I was just wondering if this isn't exposed on purpose. Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
