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
![](/manual/borland-software/jbuilder-2005/server-user-manual/images/img-3.png)
Chapter 1: Introduction 1
Chapter
1
Chapter 1Introduction
Developing Applications for J2EE Servers introduces you to the various technologies
that make up the Java™ 2 Platform, Enterprise Edition (J2EE™), explains why they
are important, and describes how you can use JBuilder to create J2EE applications
that target your application server. You’ll learn how to configure JBuilder to work with
your server, and how to accomplish the essential programming tasks of running your
applications, debugging them remotely, and deploying them to your server.
Documentation conventions
The Borland documentation for JBuilder uses the typefaces and symbols described in
the following table to indicate special text.
Table 1.1 Typeface and symbol conventions
Typeface Meaning
Bold Bold is used for java tools, bmj (Borland Make for Java), bcj (Borland
Compiler for Java), and compiler options. For example: javac, bmj,
-classpath.
Italics Italicized words are used for new terms being defined, for book titles, and
occasionally for emphasis.
Keycaps This typeface indicates a key on your keyboard, such as “Press Esc to
exit a menu.”
Monospaced type
Monospaced type represents the following:
■ text as it appears onscreen
■ anything you must type, such as “Type Hello World in the Title field
of the Application wizard.”
■ file names
■ path names
■ directory and folder names
■ commands, such as SET PATH
■ Java code
■ Java data types, such as boolean, int, and long.
■ Java identifiers, such as names of variables, classes, package
names, interfaces, components, properties, methods, and events
■ argument names
■ field names
■ Java keywords, such as void and static