Committed! Thanks :)

On Fri, Aug 28, 2009 at 10:12 PM, Everett Muniz <[email protected]>wrote:

> Unless I'm missing something I think you nailed it!  Thanks James!
> In case you're interested I've included the modified IdentityPart.cs that
> we use.  To be safe I used the most recent version of the source from just a
> few minutes ago and updated it with our changes.  This shows how we're
> leveraging NHibernate's support for excluding the name attribute from the
> <id> element.  I also Included our subclass of the ClassMap.cs where we add
> the signature for using the modified IdentityPart.cs.
>
>
> On Fri, Aug 28, 2009 at 12:18 PM, James Gregory 
> <[email protected]>wrote:
>
>> Excellent, I really appreciate the time you've put into this.
>> Try another update. I'll kick myself it this works ;)
>>
>>
>> On Fri, Aug 28, 2009 at 3:34 PM, Everett Muniz <[email protected]>wrote:
>>
>>> Thanks for your time on this James.
>>>
>>> I should have made more of a point of my slightly custom scenario from
>>> the start, sorry about that.  I'm not using a custom build.  I'm actually
>>> using the most recent binaries from the site but the architecture allows me
>>> to slip in a slightly modified IdentityPart through a really simple subclass
>>> of ClassMap.
>>>
>>> In any case, I took my custom identity out of play and I still got the
>>> error.
>>>
>>> So, I did some more work on it and I've reproduced the issue in the test
>>> with my name in the attached copy of SubclassPersistenceModelTests.cs.  It
>>> looks like it's an issue with mixing the old subclass approach and the new
>>> approach.
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Fluent NHibernate" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/fluent-nhibernate?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to