Hmm, so I am guessing we have no unit tests for that code? With all that reflection, it seems pretty fragile.
On Mon, Feb 2, 2009 at 6:58 AM, James Gregory <[email protected]>wrote: > Ok, I've committed a fix for this. Let me know if anything else crops up. > > On Sun, Feb 1, 2009 at 7:52 PM, James Gregory <[email protected]>wrote: > >> Damn! Good catch, I'll look at this ASAP. >> >> >> On Sun, Feb 1, 2009 at 7:42 PM, Duarte Nunes <[email protected]> wrote: >> >>> >>> Hi, >>> >>> I was trying to use the auto mapping feature, but was getting a >>> NullPointerException when the auto mapper was dealing with a many-to- >>> many relationship. Tracking the problem, the exception was being >>> thrown at ManyToManyAutoMapper.Map<T>, on the line: type.GetMethod >>> ("IsInverse").Invoke(manyToManyPart, new object[0]). Since the source >>> contains only methods named "Inverse", I believe this might be a bug. >>> >>> Best regards, >>> Duarte >>> >>> >>> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
