In the directory docs/examples, you will find a set of examples demonstrating JBoss Messaging working in various examples
Before running these examples, you must deploy the example-destinations located under /docs/examples/destinations
This example shows a simple send and receive to a remote queue using a JMS client
This example shows a simple send and receive to a remote topic using a JMS client
This example demonstrates usage of an EJB2.1 MDB with JBoss Messaging
This example demonstrates usage of an EJB3 MDB with JBoss Messaging
This example demonstrates an EJB2.1 stateless session bean interacting with JBoss Messaging
This example demonstrates rollback and redelivery occuring with an EJB2.1 MDB
This example demonstrates a JMS client interacting with a JBoss Messaging server using SSL encrypted transport
This example demonstrates a JMS client interacting with a JBoss Messaging server tunneling traffic over the HTTP protocol
This example demonstrates JBoss web-service interacting with JBoss Messaging
This example demonstrates a JMS client interacting with a JBoss Messaging distributed queue - it requires two JBoss AS instances to be running
This example demonstrates a JMS client interacting with a JBoss Messaging distributed topic - it requires two JBoss AS instances to be running
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
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
It is highly recommended that you familiarise yourself with the examples.
Make sure you start the JBoss server(s) before running the examples!
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