Server User Manual
Table Of Contents
- Developing Applications for J2EE™ Servers
- Contents
- Ch 1: Introduction
- Ch 2: Programming for the Java 2 Platform, Enterprise Edition
- Ch 3: Creating applications with J2EE technologies
- Ch 4: Configuring the target server settings
- Ch 5: Using JBuilder with Borland servers
- Configuring Borland servers in JBuilder
- Making the ORB available to JBuilder
- Configurations, partitions, partition services, and J2EE APIs
- Starting the configuration or server
- Remote deploying
- Remote debugging
- Web module workarounds
- Displaying the Borland Management Console in JBuilder
- International issues
- Borland servers and JDataStore 7.0
- Ch 6: Using JBuilder’s CORBA tools
- Ch 7: Using JBuilder with BEA WebLogic servers
- Ch 8: Using JBuilder with IBM WebSphere servers
- Ch 9: Using JBuilder with JBoss servers
- Ch 10: Using JBuilder with Tomcat
- Ch 11: Editing J2EE deployment descriptors
- Ch 12: Integrating with Enterprise Information Systems
- Ch 13: Building J2EE modules
- J2EE modules
- Setting module build properties
- Adding custom file types
- Sample build scenarios
- EJB JAR without any bean classes
- EJB JAR with custom files
- EJB JAR without EJB designer XML descriptors
- WAR with custom descriptor(s) in the WEB-INF directory
- WAR without any classes
- WAR with custom class filters
- WAR with custom file types
- EAR with custom files
- RAR with classes and dependencies
- Application client module with classes and dependencies
- Improving module build performance
- Index
Chapter 13: Building J2EE modules 117
Adding custom file types
■
A connector module RAR by default contains only descriptors. Classes in the
project’s output are not included.
■
An application module EAR by default contains descriptors and archive files defined
in the descriptor. The Java class type is excluded by default.
Note To add custom classes to a module, you must remove the Java class file type filter (if it
is included by default for the module) before you add a custom Java class include filter.
The default Java class file type filter includes all classes in the project, which overrides
any custom include class filters.
Clean filters
You add clean filters using the Clean page of the Properties dialog box for a module.
Clean filters control which files are deleted in the module directory before the module is
rebuilt whenever you choose either the Rebuild Project or the Rebuild Module context
menu command. A number of clean filters (exclude filters) are added to prevent the
deletion of mandatory files, such as descriptors, CVS content, and so on. Be sure that
you add the appropriate exclude clean filters to prevent the deletion of any custom
content added manually to the module directory (such as custom descriptors that
JBuilder does not recognize).
Dependencies
Use the Content|Dependencies page of the Properties dialog box for a module to add
libraries to the module. This page lists all libraries in a project including dependent
libraries. These are the default values for J2EE modules:
■
EJB modules: All libraries are excluded by default. Including a library will expand the
library inside the EJB JAR.
■
Web modules: All libraries except the server libraries (Client and Servlet) are
included in the WAR. Including a library will include the JAR in the WAR’s WEB-INF/
lib directory.
■
Connector modules: All libraries are excluded by default. Including a library will
include the JAR inside the RAR (at the root level).
■
Application client modules: All libraries are excluded by default. Including a library
will expand the library inside the JAR.
■
Application modules: All libraries are excluded by default. Including a library will
include the JAR inside the EAR (at the root level). Use the Application|Other page of
the Properties dialog box for the application module to include files in a specific
directory structure inside an EAR.
Adding custom file types
You can add custom file types to the file types that JBuilder recognizes:
1 Choose Tools|Preferences.
2 Select the Browser|File Types page.
3 Select Generic Resource File in the Recognized File Types list box.
4 Click the Add to display the Add Custom Extension dialog box.
5 Enter the new file extension in the dialog box and choose OK.
The extension you specified appears in the Associated Extensions list.
Note Create all resource files in the project’s source path to ensure that a resource file is
copied over to the project’s output path and to the module directory.