Chapter 20.
Defining the Client Deployment Descriptor
This chapter is for the Client component provider; that is, the person in charge of developing the Client
components on the client side.
20.1. Principles
The Client component programmer is responsible for providing the deployment descriptor associated
with the developed client components.
The
client
component
provider’s
responsibilities
and
the
Application
Assembler’s
responsibilities are to provide an XML deployment descriptor that conforms to the
deployment descriptor’s XML DTD as defined in the Java Application Client Specification
Version
1.4.
(Refer
to
$JONAS_ROOT/xml/application-client_1_4.xsd
or
http://java.sun.com/xml/ns/j2ee/application-client_1_4.xsd.)
To customize the Client components, information not defined in the standard XML deployment de-
scriptor may be needed. Such information might include, for example, the mapping of the name of
referenced resources to its JNDI name. This information can be specified during the deployment phase
within another XML deployment descriptor that is specific to JOnAS. The JOnAS-specific deploy-
ment descriptor’s XML schema is located in
$JONAS_ROOT/xml/jonas-client_X_Y.xsd
. The
file name of the JOnAS-specific XML deployment descriptor must be
jonas-client.xml
.
JOnAS interprets the
¶
!DOCTYPE
·
tag at the parsing of the deployment descriptor XML files. The
parser first tries to get the specified DTD via the classpath, then it uses the specified URL (or path).
The parser gets the specified schema via the classpath (schemas are packaged in the
$JONAS_ROOT/lib/common/ow_jonas.jar
file).
The standard deployment descriptor (
application-client.xml
) should contain structural infor-
mation that includes the following:
•
A Client description
•
Environment entries
•
EJB references
•
Resource references
•
Resource env references
•
The callback handler to use.
The JOnAS-specific deployment descriptor (
jonas-client.xml
) may contain information that in-
cludes the following:
•
The JNDI name of the external resources referenced by a Client component
•
The JNDI name of the external resources environment referenced by a Client component
•
The JNDI name of the beans referenced by a Client component
•
The security aspects including the JAAS file, the JAAS entry, and a login/password to use for a
specific callback handler.
Summary of Contents for Application Server
Page 1: ...Red Hat Application Server JOnAS User Guide ...
Page 8: ......
Page 22: ...14 Chapter 1 Java Open Application Server JOnAS a J2EE Platform ...
Page 58: ...50 Chapter 3 JOnAS Configuration ...
Page 66: ...58 Chapter 5 JOnAS Class Loader Hierarchy ...
Page 78: ...70 Chapter 6 JOnAS Command Reference ...
Page 80: ......
Page 86: ...78 Chapter 7 Developing Session Beans ...
Page 136: ...128 Chapter 9 Developing Message Driven Beans ...
Page 142: ...134 Chapter 10 Defining the Deployment Descriptor ...
Page 148: ...140 Chapter 11 Transactional Behavior of EJB Applications ...
Page 158: ...150 Chapter 14 EJB Packaging ...
Page 162: ...154 Chapter 15 Application Deployment and Installation Guide ...
Page 164: ......
Page 176: ...168 Chapter 18 WAR Packaging ...
Page 178: ......
Page 184: ...176 Chapter 20 Defining the Client Deployment Descriptor ...
Page 186: ...178 Chapter 21 Client Packaging ...
Page 188: ......
Page 192: ...184 Chapter 23 EAR Packaging ...
Page 194: ......
Page 200: ...192 Chapter 24 JOnAS Services ...
Page 204: ...196 Chapter 25 JOnAS and the Connector Architecture ...
Page 222: ...214 Chapter 27 Ant EJB Tasks Using EJB JAR ...
Page 234: ...226 Chapter 29 Web Services with JOnAS ...
Page 236: ......
Page 260: ...252 Chapter 34 How to use Axis in JOnAS ...
Page 270: ...262 Chapter 36 Web Service Interoperability between JOnAS and BEA WebLogic ...
Page 296: ......