Chapter 4. Running the Examples
In the directory docs/examples, you will find a set of examples demonstrating JBoss Messaging working in various examples. To run the example, navigate to the folder in a command line prompt, and type ant. Apache Ant and your JBoss installation path must pe present in your evironment path variable, in order to be able to run the example. Make sure you start the JBoss server before trying to run these examples.
docs/example/queue
This example shows a simple send and receive to a remote queue using a JMS client
docs/example/topic
This example shows a simple send and receive to a remote topic using a JMS client
docs/example/mdb
This example demonstrates usage of an EJB2.1 MDB with JBoss Messaging
docs/example/ejb3mdb
This example demonstrates usage of an EJB3 MDB with JBoss Messaging
docs/example/stateless
This example demonstrates an EJB2.1 stateless session bean interacting with JBoss Messaging
docs/example/mdb-failure
This example demonstrates rollback and redelivery occuring with an EJB2.1 MDB
docs/example/secure-socket
This example demonstrates a JMS client interacting with a JBoss Messaging server using SSL encrypted transport
docs/example/http
This example demonstrates a JMS client interacting with a JBoss Messaging server tunneling traffic over the HTTP protocol
docs/example/web-service
This example demonstrates JBoss web-service interacting with JBoss Messaging
docs/example/distributed-queue
This example demonstrates a JMS client interacting with a JBoss Messaging distributed queue - it requires two JBoss AS instances to be running
docs/example/distributed-topic
This example demonstrates a JMS client interacting with a JBoss Messaging distributed topic - it requires two JBoss AS instances to be running
docs/example/stateless-clustered
This example demonstrates a JMS client interacting with clustered EJB2.1 stateless session bean, which in turn interactes with JBoss Messaging. The example uses HAJNDI to lookup the connection factory
docs/example/bridge
This example demonstrates using a message bridge. It deploys a message bridge in JBoss AS which then proceeds to move messages from a source to a target queue
The non clustered examples expect a JBoss AS instance to be running with all the default settings. The clustered examples expect two JBoss AS instances to running with ports settings as per ports-01 and ports-02. For each example, you can always override the default ports it will try to connect to by editing jndi.properties in the particular example directory.