Package mapping for Java (Java code)
For each Package, ACS generates a subfolder in the working directory.
|
A Java package is represented in the model by a Namespace package. Use Folder Packages for library paths.
|
Child items:
| Reverser Notes: When reverse engineering code, used built in Java types are created in the Model (directly scoped to the Model) if they are not present. |
Example code:
// The working directory is C:/Work
// File C:/Work/package1/package2/foo.java
package package1.package2;
public class foo
{
// ...
}
• If the Package owns
Type Definitions of type Enumeration, ACS generates each Type Definition in the folder created for the Package. For Type Definition mapping information, see
Type definition mapping for Java (Java code).
Properties:
• The Name property is generated as the name of the Java package and folder.
| ACS may modify the folder name to make it valid for Java. You can specify the exact folder name through the CODE_GENERATION_NAME property of a Package. Tell me more... |
• The Mapping property determines specifies whether the Package models a Java Package (Namespace mapping) or a folder (Folder mapping). Irrespective of the mapping, a folder is always generated for a Modeler Package.