I would like this very much! What i dont like in the current implementation of Fluent NHibernate is that the naming of the mapping property's are dose not follow the naming in NHibernate Xml Mapping. This has the disadvantage that i can not use 100% of the existing NHibernate documentation. And i dont think that names like "References" are easyer to understand then "Many2One".
Tuna Toksöz schrieb: > Hello all, > > Me and my friend Oguz want to start a new project about NHibernate Fluent > Mapping. If we show some progress and reach to a point where we let people > use, the project can become part of Core or Contrib if other committers > want. > > There is one project on fluent mapping called Fluent NHibernate which does > its job well, but it creates XML behind the scenes, which I don't like > > I have committer access so when needed I can extend the core according to > needs. Currently Configuration & Mappings depends on XML which is not a good > idea and needs improvement. > The extension points will also allow other ways of mapping including DSLs. > > Now it comes to the questions: > > Do you think it would be beneficial to the community, or are we just > duplicating things. I will talk with Fluent NH Team to see how they can > help, and how we can help. > Do you like how NH Fluent handles mapping, in other words, inheritance, or > do you prefer real fluent interfaces? > > Thanks all. >
