After updating to 1.2.0RC2 from 1.2.0RC1 it appears that SetDefaultAssembly and SetDefaultNamespace have stopped working. Can someone confirm?



using these parameters when I load the A.B assembly



I get the following error when NHibernate tries to load the mappings from the assembly.

"These classes extend unmapped classes
ResidenceAddress extends A.B.DomainModel.Address, A.B"

A.B.DomianModel.Address is mapped as "Address" with the namespace removed so I can use the default namespace. ResidenceAddress also is in the namespace A.B, but the namespace is removed in the mapping file.

The code base remains unchanged, the only difference is the NHibernate dlls.

I am missing something?

I found a work around that works. Instead of setting the global default namespace and assemblies like before, I can set it on a HBM by HBM file basis.



While not the solution I'm looking for, it is viable for now.

I don't understand what the problem is... can you post the mappings here and also tell us how you expect it to work?

The problem is not in SetDefaultAssembly/SetDefaultNamespace, but in changes made to the way extends attribute is handled.

Thanks Sergey. It appears you are correct, the problem seems to be in the extends statement.

In both RC1 and RC2 I set the default namespace to A.B and assembly to A.B as well.

Here is the base class. Notice how the namespace and assembly are not included in the class name.

This class does the extending. Note how the extends statement lists the base class by its fully qualified name and assembly.

This works fine in RC1.

Here is what I had to do to get it to work in RC2.
My base class remains the same with the namespace and assembly removed.

I needed to remove the fully qualified name in the extends statement. Otherwise I get the class not mapped error.


I've fixed my inconsistencies but I think I think the system should be able could find the mapped class despite the inconsistencies.