To launch the New project wizard, select [File] > [New] > [Project] from the menu. Select the project wizard that is appropriate for the module, as shown below.
Category | Project | Explanation |
|---|---|---|
EJB | EJB Project | Used to create an EJB module. |
Java EE | Application Client Project | Used to create an application client module. |
Enterprise Application Project | Used to create an EAR file. EAR files can group together EJB, Web applications, and libraries. | |
Utility Project | Used to create libraries that are shared by multiple modules. | |
JPA | JPA Project | Used to create libraries that use JPA. |
Web | Dynamic Web Project | Used to create Web application modules. |
For the contents to specify in the project wizard, refer to the following:
Project name
Specify the project name to be generated.
Project contents
Specify the storage destination of the project resources. The default location is under the workspace folder.
Target Runtime
Select the runtime that runs the Java EE application. For an Interstage Application Server Java EE container (IJServer Cluster), select [Interstage Application Server V11.1 IJServer Cluster (Java EE)].
Module version
For an EJB or Web application, etc., specify the module version.
Configuration
Set the conventions and versions that the created modules and libraries conform to. Operate the support functions such as the wizard and editor, so that they conform to the conventions and versions. For an Interstage Application Server Java EE container (IJServer Cluster), select [Default Configuration for Interstage Application Server V11.1 IJServer Cluster (Java EE)].
EAR Membership
If the modules and libraries are grouped together in an EAR file, select the enterprise application project. If the enterprise application is to be created later, it need not be selected here.
Point
When [Default Configuration for Interstage Application Server V11.1 IJServer Cluster (Java EE)] is specified in Configuration, an Interstage Application Server-specific deployment descriptor is generated when the project is created. For details on this file, refer to separate documentation concerning Interstage Application Server Java EE execution environment specifications.
Note
When an EJB project is created without [Add project to an EAR] being selected under [EAR Membership], the Session Bean wizard business interface is created in the EJB project.
When an EJB project is created with [Add project to an EAR] selected under [EAR Membership], the Session Bean wizard business interface is created in an EJB client project.
When an EJB project is created with [Add project to an EAR] selected under [EAR Membership] and without [Create an EJB Client JAR module to hold the client interfaces and classes.] being selected, the Session Bean wizard business interface is created in the EJB project.
The enterprise application project can group together modules and libraries and create an EAR file.
Refer below for specifying contents specific to the enterprise application project wizard:
Content Directory
Specify the name of the folder used to store files, apart from the Java EE module created as the project, that you want to include in the EAR file.
After the enterprise application project is created, if you want to change the Java EE module to be added to the EAR file, edit the project [Java EE Module Dependencies] property.
Point
If an EAR file is used, in addition to enabling applications to be deployed as a group, the dependency relationship between the Java EE modules in the EAR file can be defined and the work involved in setting classpaths and other tasks at the operating environment can be reduced.
When an application client is included in an enterprise application, the modules and libraries to be included in the enterprise application can be downloaded as client stubs from the Interstage Java EE Admin Console. If EJB application development and EJB client development are performed in separate environments, this function can be used to download the jar file containing the EJB interface required for EJB client development.
In order to perform build for the Java application, set the build path (classpath) in the project. Use any of the following methods to set the build path for Java EE modules and libraries:
When the runtime that runs the Java EE application is selected, that library is added to the build path. This can be set in the [Targeted Runtimes] property of the project.
The library is added by the runtime name in the build path.
The group of modules and libraries in the EAR file can reference each other's classes. This manifest classpath can be set in the [Java EE Module Dependencies] property. Set the reference target with the [Java EE Module Dependencies] property for each project.
The target is added to the build path EAR library.
In the Web application module, the library can be put under WEB-INF/lib. This specification can be set in the [Java EE Module Dependencies] property. Set the reference target with the [Java EE Module Dependencies] property for each project.
The target is added to the build path Web application library.
The build path can be set using the project [Java Build Path] property. A library added using this setting is not reflected in the operating environment. Therefore, before deployment to the application server, classpath settings may be required at the operating environment.
Point
When a dynamic Web project is selected in the [Java EE Module Dependencies] property of an enterprise application project, the two tabs [Java EE Modules] and [Web Libraries] are displayed in the [Java EE Module Dependencies] property of the dynamic Web project. The manifest classpath of the enterprise application can be set at the [Java EE Modules] tab. The WEB-INF/lib of a Web application can be set at the [Web Libraries] tab.
A Java EE application may be developed using a Java EE module that was developed by another person.
If an EAR file is to be created by an enterprise application project, the Java EE module must be imported and a Java EE module project must be created.
Select [File] > [Import] from the workbench menu, then select the file format to be imported from the [Import] wizard.
Point
If a source file is included in the imported Java EE module, the source file is stored in the project source folder created by the Import wizard. If a source file is not included in the imported Java EE module, an ImportedClasses folder is created in the project created by the Import wizard and the class file is stored in the ImportedClasses folder.
