[
http://jira.jboss.com/jira/browse/JBESB-1650?page=all ]
Tom Cunningham updated JBESB-1650:
----------------------------------
Description:
Got some notes from Narayanan Raghavan about his experience with the OracleAQ message
provider. They are using it and it is working well but the experience getting it
configured could be a little smoother :
- they needed the "full version" of cglib.jar (the full version is in the EAP)
- they found the sample jboss-esb.xml confusing - it talks about moving a message from one
OracleAQ -> another OracleAQ, and there should be a sample provided of moving a message
from OracleAQ - > JBoss Messaging
was:
Got some notes from Narayanan Raghavan about his experience with the OracleAQ message
provider. They are using it and it is working well but the experience getting it
configured could be a little smoother :
- they didn't need ojdbc14.jar (need to double check this)
- they needed the "full version" of cglib.jar (the full version is in the EAP)
- they found the sample jboss-esb.xml confusing - it talks about moving a message from one
OracleAQ -> another OracleAQ, and there should be a sample provided of moving a message
from OracleAQ - > JBoss Messaging
Clean up OracleAQ documentation
-------------------------------
Key: JBESB-1650
URL:
http://jira.jboss.com/jira/browse/JBESB-1650
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Message Store
Affects Versions: 4.2.1 CP2
Reporter: Tom Cunningham
Assigned To: Tom Cunningham
Fix For: 4.2.1 CP3
Got some notes from Narayanan Raghavan about his experience with the OracleAQ message
provider. They are using it and it is working well but the experience getting it
configured could be a little smoother :
- they needed the "full version" of cglib.jar (the full version is in the EAP)
- they found the sample jboss-esb.xml confusing - it talks about moving a message from
one OracleAQ -> another OracleAQ, and there should be a sample provided of moving a
message from OracleAQ - > JBoss Messaging
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira