Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > Java code > Reverse engineering legacy Java code > Modeling Java code in modeler > Setting up Java specific information for interfaces (Java code)
  
Setting up Java specific information for interfaces (Java code)
In addition to the standard Interface properties in Modeler, you can apply the «Java Class» stereotype to an Interface, and then use its Tag Definitions to define Java specific information.
1. If you have not done so already, add the Java Profile package to your Model. How?
2. Set the standard properties of the Interface as required. Tell me more...
3. If you want to generate a Java file for the Interface, but not generate a class definition for the Interface in that file, apply the «Java Module» stereotype to the Interface.
4. Apply the «Java Class» stereotype to the Interface.
For information about applying Stereotypes to an item, see Applying a stereotype to a model item.
5. Open the Interface's Property Pages, and then click the Java Class tab.
For information about setting the tagged value of a Tag Definition, see Setting a tagged value for an applied tag definition.
6. If you want to specify that the class has no access specifier, set the tagged value of the Java Default Access tag definition to TRUE
7. If you want to specify that the class is final, set the tagged value of the Java Final tag definition to TRUE.
8. If you want to specify a file comment, specify the text as the tagged value of the Java File Comment tag definition.
9. If the Interface is nested but you want it to be generated outside the class construct of its parent class, set the tagged value of the Java Non Member tag definition to TRUE.
10. If you want to generate import statements, use a Dependency (of Type Dependency) to link the Interface to the Packages, Classes, Data Types and Interfaces you want to import. If the items you want to import are not present in the Model, record the import statements through the Java Import Text tag definition.
11. If you want to generate extends statements, use a Generalization to link the super Interface to the sub Interface it extends. If the super Interface is not present in the Model, record the extends statements through the Java Extends Text tag definition.