To package, deploy and run this example, go to the <INSTALL>/javaeetutorial5/examples/ejb/simplemessage/ directory. Creating the Administered ObjectsThis example requires the following:
If you have run the simple JMS examples in Chapter 31 and have not deleted the resources, you already have these resources and do not need to perform these steps. You can use Ant targets to create the resources. The Ant targets, which are defined in the build.xml file for this example, use the asadmin command. To create the resources needed for this example, use the following commands: ant create-cf ant create-queue These commands do the following:
The Ant targets for these commands refer to other targets that are defined in the <INSTALL>/javaeetutorial5/examples/bp-project/app-server-ant.xml file. Building, Deploying, and Running the Application Using NetBeans 5.5To build, deploy, and run the application using NetBeans 5.5, do the following:
The output of the application client in the Output pane looks like this: Sending message: This is message 1 Sending message: This is message 2 Sending message: This is message 3 To see if the bean received the messages, check <install_dir>/domains/domain1/logs/server.log. The output from the message-driven bean appears in the server log (<JAVAEE_HOME>/domains/domain1/logs/server.log), wrapped in logging information. MESSAGE BEAN: Message received: This is message 1 MESSAGE BEAN: Message received: This is message 2 MESSAGE BEAN: Message received: This is message 3 The received messages often appear in a different order from the order in which they were sent. Undeploy the application after you finish running the client. To undeploy the application, follow these steps:
To remove the generated files, right-click the simplemessage project and choose Clean Project. Building, Deploying, and Running the Application Using AntTo create and package the application using Ant, use the default target for the build.xml file: ant This target packages the application client and the message-driven bean, then creates a file named simplemessage.ear in the dist directory. By using resource injection and annotations, you avoid having to create deployment descriptor files for the message-driven bean and application client. You need to use deployment descriptors only if you want to override the values specified in the annotated source files. To deploy the application and run the client using Ant, use the following command: ant run Ignore the message that states that the application is deployed at a URL. The output in the terminal window looks like this: running application client container. Sending message: This is message 1 Sending message: This is message 2 Sending message: This is message 3 To see if the bean received the messages, check <install_dir>/domains/domain1/logs/server.log. In the server log file, the following lines should be displayed, wrapped in logging information: MESSAGE BEAN: Message received: This is message 1 MESSAGE BEAN: Message received: This is message 2 MESSAGE BEAN: Message received: This is message 3 The received messages often appear in a different order from the order in which they were sent. Undeploy the application after you finish running the client. Use the following command: ant undeploy To remove the generated files, use the following command: ant clean Removing the Administered ObjectsAfter you run the example, you can use the following Ant targets to delete the connection factory and queue: ant delete-cf ant delete-queue |