A Java DC can contain arbitrary Java code. A Java DC does not create a deployable or installable build result. (The class files generated from the source code are stored in a temporary folder and removed after the build.) It is up to the developer to define a public part with purpose assembly, if a JAR file should be generated. The public part of purpose assembly could, for example, contain all generated class files of the DC. This public part could be used by another DC to include the build results of the Java DC into an SDA or EAR.
There are three typical public part entity types to use:
· Java Class
· Java Package
· Java Package Tree
For each of these types you can choose the subtype "Source" or "Class":
· Source will create a zip archive containing the specified sources.
· Class will create a jar file containing the specified classes.
Ў Java Classwill add one specific class
Ў Java Packagewill add all classes in the specified package
Ў Java Package Tree will add all classes in the specified package and all subpackages
Class files. It is up to the developer to define appropriate public parts if something else is required. Good practice would be to create a public part with purpose assembly containing everything and to create a public part with purpose compilation that contains the classes of the DC that make up the API.
A project for a Java DC is managed from the Java DC Explorer and the Package Explorer in the Java Perspective.