On mandag 5. september 2011 at 14:11, James Gregory wrote:
Could you show your configuration code? There were some issues with the Mappings method being called multiple times before.
--
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/-/kYDRnk8MgysJ.
To post to this group, send email to fluent-n...@googlegroups.com.
To unsubscribe from this group, send email to fluent-nhibern...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en.
On mandag 5. september 2011 at 15:55, James Gregory wrote:
Ok, that's fair enough. Nothing immediately obvious in the stack trace. Tell me, are you using Fluently.Configure? And are you creating multiple instances of it or doing everything within one?
--
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/-/aLPhyYFU0gwJ.
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.