NHibernate DuplicateMappingException when two classes have the same name but different namespaces

cdmckay picture cdmckay · Jul 21, 2009 · Viewed 10k times · Source

I have a class in my domain model root that looks like this:

namespace Domain
{
  public class Foo { ... }
}

I also have another class with the same name in a different namespace:

namespace Domain.SubDomain
{
  public class Foo { ... }
}

For my mappings, I have a Mapping directory with a subdirectory called SubDomain that contains mappings for the domain classes found in Domain.SubDomain namespace. They are all in the same assembly.

However, when I try to load them with NHibernate, I keep getting a DuplicateMappingException... even though both Foos having different namespaces. The code I am using to load my NHibernate configuration is this:

var cfg = new Configuration()
  .Configure()                
  .AddAssembly("Domain");   

How can I tell NHibernate to let me use two entities with the same name (but different namespaces)?

Answer

cdmckay picture cdmckay · Aug 29, 2009

I found the answer on the Hibernate website:

If you have two persistent classes with the same unqualified name, you should set auto-import="false". An exception will result if you attempt to assign two classes to the same "imported" name.

I used that as an attribute for the <hibernate-mapping> tag and it worked.