Seconded. This isn't the kind of thing you can really do until we uncouple the mapping from the hbm.xml.
On Fri, Jan 9, 2009 at 1:58 AM, Paul Batum <paul.ba...@gmail.com> wrote: > Hi Chris, > > I am afraid that in its current state, even if the mappings were publicly > accessible, you would struggle to extract all the necessary data from them. > It is further complicated by the fact that you would want to access the data > AFTER conventions have been applied, but in some cases the conventions only > modify the output xml, not the model itself. > > I would encourage you to pull the source down, change it to public and try > working against it - I suspect you will find that this is not quite as > simple as making the mappings public. > > Paul Batum > > > On Fri, Jan 9, 2009 at 5:30 AM, Chris Bilson <cbil...@gmail.com> wrote: > >> >> Sorry, subject should be "Persist_ence_Model" >> >> On Jan 8, 10:30 am, Chris Bilson <cbil...@gmail.com> wrote: >> > 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 -~----------~----~----~----~------~----~------~--~---
