Bug 778594 (SOA-1067)

Summary:	Services Guide refers to JBossMQ which is no longer the default
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Dana Mison <dmison>
Component:	Documentation	Assignee:	Dana Mison <dmison>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 GA
Target Milestone:	---
Target Release:	4.3 CP01
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1067
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-02-20 18:45:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	778605, 778710

Description Dana Mison 2008-12-08 02:23:58 UTC

Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2009-02-20 13:45:12
project_key: SOA

Chapter 12, refers to JBossMQ which is not longer included.  Content needs to be updated to reflect this.

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 it should 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.

Comment 1 Dana Mison 2008-12-08 02:24:23 UTC

Link: Added: This issue is related to JBESB-2222

Comment 2 Dana Mison 2008-12-15 02:56:08 UTC

Link: Added: This issue is a dependency of SOA-1078

Comment 3 Dana Mison 2008-12-15 04:40:43 UTC

Link: Added: This issue related SOA-1050

Comment 4 Dana Mison 2009-01-01 04:55:59 UTC

updated

Comment 5 Dana Mison 2009-02-16 04:19:38 UTC

Link: Added: This issue is a dependency of SOA-1174

Comment 6 Dana Mison 2009-02-19 06:56:45 UTC

Release Note:
SOA-1067
All references to JBossMQ have been removed from the Services Guide as it is no longer included.

Comment 7 Len DiMaggio 2009-02-20 18:45:12 UTC

Verified in the services guide in 4.3 CP01 CR2 - the doc no longer references MQ - the text in chapter 12 now reads:

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.