J2EE
By default, this preference is off, and J2EE Modules are created one per project. By enabling this preference, modules can be added to existing projects containing other modules. The J2EE Import and Creation wizards will also react to this preference, allowing the user to specify existing projects.
Preference page
The Java Jar Dependencies properties page provides the mechanism for users to update the modules dependencies within an Enterprise Application which needs updating the module manifest (MANIFEST.MF), classpath (.classpath), project (.project) files. This property page can be launched by right click on the J2EE Module-> Properties-> Java Jar Dependencies. This Property page also includes the functionality to setup java utility projects as Web Library projects for standalone and non standalone web mouules. The following screen shots depict the above mentioned functionality
Jar Dependency property page on Web Module:
Web Library Setting on Web module:
Web Library Setting on Standalone Web module:
The EAR Modules properties page provides the mechanism for users to add the J2EE Modules within an Enterprise Application. This property page can be launched by right click on the EAR Module-> Properties-> EAR Modules. The Java project can be selected in this property page and they are converted to a utility jar module.The following screen shots depict the above mentioned functionality.
EAR Modules page:
This wizard is used for importing ear archives into the workbench as ear modules. All the nested j2ee archives in the EAR are imported as individual j2ee modules and the names of the nested j2ee archives imported as j2ee modules can be configured in the third page of the wizard. Any utility jars that exist in the ear can optionally be imported as java projects from the second page of the wizard.
EAR Import Wizard
EAR Import wizard page 1:
EAR Import wizard page 2:
EAR Import wizard page 3:
The EJB import wizard is used to import ejb jars as ejb modules into the workbench. All other module types (Application Client,Web,Connector) import wizards look and work similiar to the ejb jar import wizard. To launch the import wizards right click on any modules folders in the j2ee project explorer and select Import
EJB Jar Export Wizard:
The EAR export wizard is used for exporting EAR modules from the workbench to deployable ear archives. The ear export packages all the nested modules inside the ear into their respective module archives. The screen shot below shows the wizard, the user can optinally export all source and can optionally overwirte an existing ear file. These options are turned off by default. One common way to launch the export wizard is in the j2ee project explorer right click on a EAR module and select Export-> EAR file
EAR Export Wizard:
The EJB export wizard is used for exporting ejb modules into deployable ejb jar files. All other j2ee modules types (Application Client, Web, Connector) have similar export wizards and one common way to launch the wizard is to right click on the module and select Export and selecting the corresponding module file type export (e.g EJB Jar File, War File etc..)
EJB Jar Export Wizard:
All the J2EE module (EAR,Application Client,Web,EJB,Connector) validators are functionally working in this milestone release. The J2EE validators can be run manually on J2EE modules by right clicking on the module in the j2ee explorer view and selecting Run Validation.They run automatically on incremental builds if the auto build setting in the workbench turned on