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 115
Chapter
13
Chapter 13Building J2EE modules
This chapter presents specific information about packaging J2EE modules in JBuilder.
It explains about setting module build properties, including the use of custom filters and
file types. It also provides a few common build scenarios and tips for improving build
performance.
J2EE modules
You can create J2EE modules in JBuilder using the wizards available in the object
gallery (File|New). JBuilder recognizes the following types of J2EE modules:
■
Web — A Web module contains all the compiled source files, resources, and
deployment descriptors needed to deploy a web application. You can create web
modules using JBuilder’s web wizards and tools. Once you compile the web
module, a WAR file is created. For complete information about web modules, see
Developing Web Applications.
■
EJB — An EJB module contains all the compiled source files, resources, and
deployment descriptors needed to deploy one or more enterprise beans. You can
create enterprise beans using JBuilder’s EJB wizards and tools. Once you compile
the EJB module, a JAR file is created. For complete information about creating EJB
modules and enterprise beans, see “Creating session beans with the EJB designer”,
“Creating beans with the Enterprise JavaBean 1.x wizard”, “Creating entity beans
with the EJB designer”, and “Creating EJB 1.x entity beans from an existing
database table.” All these chapters are in the Developing Applications with
Enterprise JavaBeans book.
■
Application client — An application client module contains all the resources and
deployment descriptors for a client application that references one or more
enterprise beans. Create the module using the File|New|Enterprise|Application
Client Module wizard. Compiling an application client module creates a JAR file. For
more specific information about creating application client modules and editing the
deployment descriptors, see “Creating an application client module” in the
“Developing enterprise bean clients” chapter of Developing Applications with
Enterprise JavaBeans.
■
Connector — A connector module contains the resource adapter and deployment
descriptors that connect the selected application server with an existing enterprise
information system. Create a connector module using the File|New|Enterprise|