sergey wrote:
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.
Code:
<class name="Address" table="Address" lazy="false">
This class does the extending. Note how the extends statement lists the base class by its fully qualified name and assembly.
Code:
<joined-subclass name="ResidenceAddress" extends="A.B.Address, A.B" table="ResidenceAddress" .../>
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.
Code:
<class name="Address" table="Address" lazy="false">
I needed to remove the fully qualified name in the extends statement. Otherwise I get the class not mapped error.
Code:
<joined-subclass name="ResidenceAddress" extends="Address" table="ResidenceAddress" .../>
I've fixed my inconsistencies but I think I think the system should be able could find the mapped class despite the inconsistencies.