[TUSCANY-1250] Static SDO generator generates an erroneous factory class, when inheritance and different Java packages are used

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Java-SCA-M2
• Fix Version/s: Java-SDO-1.0
• Component/s: Java SDO Tools
• Environment: WinXP (tested with Java-SDO-M2 and Java-SDO-M3-RC3)
• Assignee: Unassigned
• Reporter: Daniel Peter
• Created: 07/May/07 10:13
• Updated: 19/Sep/10 11:25
• Resolved: 08/May/07 21:53

Description

The static SDO generator generates an erroneous factory class, when inheritance and different Java packages are used.

The initializeMetaData() method in my generated FactoryImpl class has this piece of code:
...
// Obtain other dependent packages
SdtFactoryImpl theSdtPackageImpl_1 =
(SdtFactoryImpl)FactoryBase.getStaticFactory(SdtFactoryImpl.NAMESPACE_URI);
...
// Add supertypes to types
addSuperType(myClassType, mySuperClassType);
...

But the variable "mySuperClassType" cannot be resolved at this point, because it is defined in a different package.
The code probably should look like this:
addSuperType(myClassType, theSdtPackageImpl_1.getMySuperClass());

I noticed this bug when using M3-RC3, where the -noEmf option is always turned on.
The factory/package code is correctly generated with M2, if the -noEmf option is NOT specified, but the same error occurs when the -noEmf option is specified with M2.