[esb-issues] [JBoss JIRA] Commented: (JBESB-1952) update readme.txt in samples/quickstarts/helloworld_action/oracle-aq
[
https://jira.jboss.org/jira/browse/JBESB-1952?page=com.atlassian.jira.plu...
]
Mike T. commented on JBESB-1952:
--------------------------------
You may want to include a sample Oracle script to create the queue table, create the
queue, and enable the queue:
exec dbms_aqadm.CREATE_queue_table(queue_table => 'myqueue_table_name',
multiple_consumers => FALSE, queue_payload_type => 'SYS.AQ$_JMS_MESSAGE');
exec dbms_aqadm.CREATE_queue(queue_name => 'myqueue_name', queue_table =>
'myqueue_table_name');
exec dbms_aqadm.start_queue( queue_name =>'myqueue_name' ,enqueue => true
,dequeue => true );
update readme.txt in samples/quickstarts/helloworld_action/oracle-aq
--------------------------------------------------------------------
Key: JBESB-1952
URL: https://jira.jboss.org/jira/browse/JBESB-1952
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Examples
Environment: This has been found in JBoss ESB 4.3. Very possible that newer
versions have the same issue.
Reporter: Mike T.
the readme.txt file located in samples\quickstarts\helloworld_action\oracle-aq which
includes instructions on setting up Oracle AQ as a JMS provider needs to be updated:
- jndi.properties file does not need to be edited as per step 2. jboss-esb.xml needs to
be edited.
- lib/ext/jms/oracleaq folder does not exist in the distribution. It would recommended to
include them or include links to where they can be downloaded from.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira