[
https://jira.jboss.org/jira/browse/JBESB-2222?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-2222.
-------------------------------
Resolution: Rejected
JbossMQ is the default in AS 4.2.2 and, I believe, is still the default in AS 4.2.3.
The documentation within the ESB should refer to the server project releases and not to
the platform releases.
jBPM Integration Guide & Services Guide refers to JBossMQ which
is no longer the default
----------------------------------------------------------------------------------------
Key: JBESB-2222
URL:
https://jira.jboss.org/jira/browse/JBESB-2222
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Documentation
Affects Versions: 4.4, 4.2.1 CP4
Reporter: Darrin Mison
I spotted this in the SOA 4.2.CP03 jBPM Integration Guide & 4.3 Services Guide both
of which source their content from the ESB docs
This service listens to the jBPMCallbackBus, which by default is a JMS Queue on either a
JBossMQ
(jbmq-queue-service.xml) or a JbossMessaging (jbm-queue-service.xml) messaging
provider. Make sure only one of these files gets deployed in your jbpm.esb archive. If
you want to
use your own provider simple modify the provider section in the jboss-esb.xml to
reference your
JMS provider.
Since JBossMQ is nolonger the default, I have changed the SOA docs to say:
This service listens to the jBPMCallbackBus, which by default is a JMS Queue using the
JbossMessaging (jbm-queue-service.xml) messaging
provider. If you want to use your own provider simple modify the provider section in
the jboss-esb.xml to reference your JMS provider.
This should be updated in the ESB source docs
--
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