Java Reference
In-Depth Information
Equipment: Laptop
Office number: 186
Waiting for 3 message(s)
New hire event processed:
Employee ID: 54
Name: Joe Lawrence
Equipment: Java Phone
Office number: 135
Waiting for 2 message(s)
New hire event processed:
Employee ID: 50
Name: Bill Tudor
Equipment: Desktop System
Office number: 200
Waiting for 1 message(s)
New hire event processed:
Employee ID: 51
Name: Carol Jones
Equipment: Laptop
Office number: 262
The output from the message-driven beans and the entity class appears in the server log,
wrapped in logging information.
For each employee, the application first creates the entity and then finds it. You may see
runtime errors in the server log, and transaction rollbacks may occur. The errors occur if
both of the message-driven beans discover at the same time that the entity does not yet
exist, so they both try to create it. The first attempt succeeds, but the second fails because
the bean already exists. After the rollback, the second message-driven bean tries again
and succeeds in finding the entity. Container-managed transactions allow the application
to run correctly, in spite of these errors, with no special programming.
To Run the
clientmdbentity
Example Using Ant
1. Go to the following directory:
tut-install
/examples/jms/clientmdbentity/
2. To compile the source files and package the application, use the following
command:
ant
The
ant
command creates the following:
• An application client JAR file that contains the client class and listener class
files, along with a manifest file that specifies the main class
