Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > Transformation Development Kit (TDK) > Customizing an ACS Code Generator DLL > Customizing a TDK code generation transformation patterns model - current TDK models > Changing code generation definition in a TDK code generation transformation patterns model > Define and use additional metaclasses (TDK)
  
Define and use additional metaclasses (TDK)
If you have classes in your application model, and two stereotypes <<GreenClass>> and <<RedClass>>, you can apply the stereotypes to your classes.
If you want a separate meta class <<4Meta>> to collect the standard classes, the <<GreenClasses>> and the <<RedClasses>>, in a particular way, you can connect the 4G yellow classes to these meta classes.
1. Check that the <<4Meta>> is associated to a tag definition named “4GSearchAs”. If it is not, (which happens with an obsolete 4G profile), create a Rich Text tag definition “4GSearchAS” and associate it to the <<4Meta>> stereotype.
2. In the generator model, define a standard Class class, stereotyped with <<4Meta>>.
3. In the generator model, in the same package as Class, add two new classes; RedClass and GreenClass.
4. Set the tag definition 4GSearchAs for GreenClass to the following: %search(“ “, “Class”, “RedClass”).
5. Set the tag definition 4GSearchAs for GreenClass to the following: %search (“ “, “Class”, “GreenClass”).
6. Important: Turn off potential unwanted items that may still be mapped to the meta class Class. The list of objects identified by meta classes that are supposed to have the same type in Modeler must be exclusive. To do this, define an operation on class on the Class meta class named ExtendedSet() and returning a %list, and set its body to return to %return” “.