I agree with Paul, our codebase changes way too rapidly to build a tool so
dependent on it. Maybe when things stabilise and we enter into a regular
release cycle then it might be achievable, but that isn't going to be for a
while yet.
I'd definitely suggest using automapping if at all possible.

On Wed, Feb 4, 2009 at 8:53 AM, Paul Batum <paul.ba...@gmail.com> wrote:

> I like the idea of a tool that will generate class maps based on hbm xml,
> but I suspect that the significant amount of change that our API is
> currently undergoing is a barrier. Keeping the tool up to date could be
> quite a burden.
>
> Have you already ruled out automapping?
>
>
> On Wed, Feb 4, 2009 at 2:13 PM, bbehrens <brandonbehr...@gmail.com> wrote:
>
>>
>> I was wondering if any of the project owners would like to have a
>> ClassMap<T> generator.  The idea is you take existing .hbm files and
>> it creates the ClassMaps for you.  Exactly like you can go from
>> ClassMap files to .hbm files.
>>
>> I've been looking hard at FNH for the past week or so.  I showed it to
>> one of my team members and his first response was "you mean we'd have
>> to go through that mapping process again?"  I thought about it figured
>> one of the major benefits of FNH is you can get away from the mapping
>> files.  Why not make the barrier of entry less painful for people
>> wanting to go with FNH over traditional .hbm mapping files?
>>
>> I'm going to write some a patch for our internal use that will do
>> that.  I would be happy to contribute the code to the project if there
>> is any interest.
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to