Server User Manual

116 Developing Applications for J2EE Servers
Setting module build properties
Connector Module wizard. Compiling a connector module creates a RAR (Resource
Archive) file. For more specific information about creating connector modules and
editing the deployment descriptors, see Chapter 12, “Integrating with Enterprise
Information Systems.”
■
Application — An application module can contain any of the other types of J2EE
modules and wraps them into a single application and includes its own deployment
descriptor entries. Create an application module using the File|New|Enterprise|
Application Module wizard. Compiling an application module creates an EAR
(Enterprise Archive) file. For more specific information about creating application
modules and editing the deployment descriptors, see “Creating an application
module” in the “Deploying enterprise beans” chapter of Developing Applications with
Enterprise JavaBeans.
■
JBoss service — A JBoss service module contains the definition of a service. Once
you compile the service module, a service archive (SAR) is created, ready to be
deployed to JBoss. For information about creating a JBoss service module, see
“Creating a JBoss service module” on page 84
Setting module build properties
The content of an archive is controlled by a combination of node level properties (filters
for file types and classes and dependencies). The content of the archive will match the
content of the module directory. To begin editing the properties of a module, right-click
the module in the project pane and choose Properties on the context menu.
File type filters
In the Properties dialog box for a module, the Content page contains a list of include file
type filters that control which file types are copied over from the project’s output path to the
module directory before the archive is created. The file types listed here match the global
file types recognized by JBuilder. (See Tools|Preferences|Browser|File Types.) Each
module has a list of pre-selected file type filters depending on the type of module. For
example, the EAR module has only the Archive and the XML file type selected by default.
The file types therefore work in combination with the include and exclude filters. For
example, if you add a recursive exclude filter for a certain file type, it will override the
file type filter selection.
Class and resource filters
You can customize archive content using custom filters. Add filters on the Content
page of the Properties dialog box for a module. The following default rules apply for the
different module types:
■
EJB JAR content is by default controlled by the classes defined in the module
descriptors and dependent classes. You must add any other classes using custom
filters. The Java Class file type is included by default. To turn off this behavior,
uncheck the option Only Include Module Specific Java Classes and add custom filters.
■
Web JAR content is by default controlled by the classes defined in the module
descriptors and dependent classes. You must add any other classes using custom
filters. The Java Class file type is included by default. To turn off this behavior,
uncheck the option Only Include Module Specific Java Classes and add custom
filters.
■
An application client JAR by default includes all classes in the project’s output path
and the generated classes, such as IDL stubs. The Java class file type is included
by default.