Oh yeah, the model is NOWHERE NEAR complete. There is a huge amount missing. I am trying to sketch out each broad area before I start filling in the detail. I'm just finishing the work on demonstrating support for multiple nhibernate versions and then I will be moving on to conventions.
On Thu, Jan 22, 2009 at 3:54 AM, Tuna Toksoz <tehl...@gmail.com> wrote: > Hi Paul, > > I guess the mapping classes are not yet complete, i mean PropertyMapping > doesn't have Type for the property, etc. I may be missing a point, so any > pointers is highly appreciated. > > > Tuna Toksöz > http://tunatoksoz.com > > Typos included to enhance the readers attention! > > > > On Wed, Jan 21, 2009 at 5:46 PM, Tuna Toksoz <tehl...@gmail.com> wrote: > >> Ok, I will go with what you suggest and lets see what happens :) >> >> >> Tuna Toksöz >> http://tunatoksoz.com >> >> Typos included to enhance the readers attention! >> >> >> >> On Tue, Jan 20, 2009 at 1:52 PM, Paul Batum <paul.ba...@gmail.com> wrote: >> >>> Hi Tuna, >>> >>> One option is to start working with my branch. There is an integration >>> test called Should_allow_music_entities_to_be_saved which passes and uses >>> hbm. Getting it to pass using your direct NHibernate configuration approach >>> would be a step in the right direction I think. To do so, I would suggest >>> these steps: >>> >>> - Create a set of NHibernateWriter classes that are structurally the >>> same as the existing HbmWriter classes, but write to SimpleValue, >>> Property, >>> etc instead of hbm classes. >>> - Create a class that utilizes the newly created writers. It should >>> be similar to the MappingXmlSerializer. >>> - Create a custom persistence model that overrides the Configure >>> method and calls into the previously mentioned class, instead of the >>> MappingXmlSerializer. >>> >>> You should be aware, that the design I am using for the hbm writers is >>> not 'proven' yet. The goal is to have an approach that will allow multiple >>> output formats against multiple versions of nhibernate but I am yet to >>> demonstrate that this is possible. There is some risk that you will begin >>> this work only to later discover that its not going to work. I would of >>> course, like to hear your thoughts on the design. >>> >>> Paul Batum >>> >>> >>> On Tue, Jan 20, 2009 at 7:49 PM, Tuna Toksoz <tehl...@gmail.com> wrote: >>> >>>> You mentioned my name, so here is the question: I have some freetime >>>> (some weeks) that I can spend on fluent nhibernate and I don't know where >>>> to >>>> start. Create a seperate branch and work there or what? >>>> I also don't really know how to test them because the story goes on >>>> SimpleValue, Property classes and it is not really easy to follow what >>>> changes when for specific mapping node(property,one-to-many etc), so i >>>> believe i need some sort of integration test. >>>> >>>> What do you guys think? >>>> >>>> >>>> Tuna Toksöz >>>> http://tunatoksoz.com >>>> >>>> Typos included to enhance the readers attention! >>>> >>>> >>>> >>>> On Tue, Jan 20, 2009 at 3:04 AM, Paul Batum <paul.ba...@gmail.com>wrote: >>>> >>>>> >>>>> As a result, this code base can also support the direct nhibernate >>>>> configuration approach that Tuna is ex >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
