Red Hat Application Server, Manual

Page: 157 / 296

Chapter 14.
EJB Packaging
This chapter describes how the bean components should be packaged. It is for the Enterprise Bean
provider; that is, the person in charge of developing the software components on the server side.
14.1. Enterprise Bean Principles
Enterprise Beans are packaged for deployment in a standard Java programming language Archive file,
called an EJB-JAR file. This file must contain the following:
The beans’ class files
The class files of the remote and home interfaces, of the beans’ implementations, of the beans’
primary key classes (if there are any), and of all necessary classes.
The beans’ deployment descriptor
The EJB-JAR file must contain the deployment descriptors, which are made up of:
•
The standard xml deployment descriptor, in the format defined in the EJB
2.1 specification. Refer to
$JONAS_ROOT/xml/ejb-jar_2_1.xsd
or
http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd. This deployment descriptor must be stored
with the name
META-INF/ejb-jar.xml
in the EJB-JAR file.
•
The JOnAS-specific XML deployment descriptor in the format defined in
$JONAS_ROOT/xml/jonas-ejb-jar_X_Y.xsd
. This JOnAS deployment descriptor must
be stored with the name
META-INF/jonas-ejb-jar.xml
in the EJB-JAR file.
14.1.1. Entity Bean Example
Before building the EJB-JAR file of the Account Entity Bean example, the Java source files must be
compiled to obtain the class files and the two XML deployment descriptors must be written.
Then, the EJB-JAR file (
OpEB.jar
) can be built using the
jar
command:
cd your_bean_class_directory
mkdir META-INF
cp .../eb/*.xml META-INF
jar cvf OpEB.jar sb/*.class META-INF/*.xml