Java Reference
In-Depth Information
Vendor: committed transaction 1
Vendor: Completed processing for order 2
Vendor: sent 6 computer(s)
Retailer: Order filled
Vendor: committed transaction 2
5. After you run the client, you can delete the destination resources by using the
following commands:
asadmin delete-jms-resource jms/AQueue
asadmin delete-jms-resource jms/BQueue
asadmin delete-jms-resource jms/CQueue
asadmin delete-jms-resource jms/OTopic
An Application That Uses the JMS API with a Session Bean
This section explains how to write, compile, package, deploy, and run an application that
uses the JMS API in conjunction with a session bean. The application contains the follow-
ing components:
• An application client that invokes a session bean
• A session bean that publishes several messages to a topic
• A message-driven bean that receives and processes the messages using a durable
topic subscriber and a message selector
You will find the source files for this section in the
tut-install
/examples/jms/cli-
entsessionmdb/
directory. Path names in this section are relative to this directory.
Writing the Application Components for the
clientsessionmdb
Example
This application demonstrates how to send messages from an enterprise bean (in this case,
a session bean) rather than from an application client, as in the example in
Chapter 11
, “
A
Message-Driven Bean Example
.
”
Figure 21-3
illustrates the structure of this application.
