I know of at least one other hole in the duplicate mapping defense, which may or may not be the same as what you're seeing. I'm planning on pinpointing and fixing that one 'cause it's bugging me, but if can get me something reproduceable, I'll look at yours while I'm there.
On Wed, Sep 7, 2011 at 4:24 AM, James Gregory <[email protected]>wrote: > The two stack traces show that the first is running through the automapper, > and the second just a regular persistencemodel. I can't remember this part > off the top of my head, but it does sound like it's intentional. > > It's quite difficult to give you any more help without either seeing how > you're adding the mappings, or getting my hands on a reproduction. FNH > *should* prevent duplicates from being added to NH, but there's obviously a > hole in that defense; if you're seeing the same assembly in ScannedSources > multiple times, then it sounds like you're adding it twice (or we've got a > bug!). Again, hard to tell which without actually seeing something, I'm > afraid. > > -- > You received this message because you are subscribed to the Google Groups > "Fluent NHibernate" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/fluent-nhibernate/-/f6EHwxskGB4J. > > 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. > -- 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.
