http://www.gg3721.com/
http://www.gg3721.com/
I'm working on a project that will involve writing a fluent interface/API for NHibernate mappings.
I would like to do this API as part of the main NHibernate trunk (2.0, or for 1.2 & 2.0) so that everyone can benefit and I won't have to maintain it separately, etc, etc, etc.
My idea was to Make the API the primary mechanism and have the XML and Attributes stuff drive the API. In fact, the attributes (which currently produce XML from what I understand) could eventually be changed to drive the API directly instead of involving the intermediate XML step.
Before I embark upon this, does anyone have any questions/comments/concerns/suggestions?
Thanks,
Chad
---------- Original message ----------
From: Jim Bolla <jim.bolla@gmail.com>
Date: Dec 12, 2007 3:28 PM
Subject: Re: [NHibernate-development] mapping in c# via fluent interface?
To: the NHibernate development list
<nhibernate-development@lists.sourceforge.net>
On Dec 12, 2007 10:09 AM, Ayende Rahien <ayende@ayende.com> wrote:
> To be clear, I 100% want to keep the XML route open. We need that for a
> whole host of reasons.
Absolutely. Same with Attributes. But I think there would be great
value in a 3rd option that doesn't require you to litter your domain
layer w/ persistence details but still gives you strong refactoring
support. That is what is cooking in my brain right now.
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Nhibernate-development mailing list
Nhibernate-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nhibernate-development