To run with Oracle AQ as your JMS provider you will need to follow the following steps:

1. Using the Oracle Enterprise Manager Console create 3 queues named:
	ACTION_REQUEST, B and HELLO_WORLD_ACTION, make sure to set 
	the payload type to Object: SYS, AQ$_JMS_MESSAGE.

2. Edit the jndi.properties file to reflect your database connection settings

3. Copy the jndi.properties and the jboss-esb.xml in the helloworld_action directory.

4. From the lib/ext/jms/oracleaq directory copy the following jars in to the
	helloworld_action/lib directory	

  26747 Mar 18 18:16 asm.jar
 286330 Mar 18 18:16 cglib-2.1_2jboss.jar
 120342 Aug  4  2006 mockejb.jar
   8757 Apr  4 14:13 org.jboss.soa.esb.oracle.aq-4.2.MR2.jar
   
   and obtain the following jars from your Oracle DB install:
   
 772466 Mar 27 11:14 aqapi13.jar  (from oracle)
1397543 Mar 27 11:13 ojdbc14.jar  (from oracle)
   

Note that 

1. Oracle AQ is using a database connection as it's JMS connection.
2. Oracle AQ does not have a JNDI provider and it is common to register
   Queues in an LDAP. Here we chose to register the Queues to MockContext
   which is why you need the mockejb.jar, as well as the asm and cglib jars
   that it depends on. The org.jboss.soa.esb.oracle.aq-4.2.MR2.jar plugin
   does the actual work of registering. Registering to JNP proved not
   possible because of code in the Oracle API to support option 1, the LDAP
   registration.