Bug 778127 (SOA-638)

Summary:	Change docs from JBoss MQ to JBoss Messaging
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	David Ward <dward>
Component:	Documentation	Assignee:	Dana Mison <dmison>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 GA	CC:	jwulf
Target Milestone:	---
Target Release:	4.3 GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-638
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	agnostic
Last Closed:	2008-10-28 07:54:02 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:

Description David Ward 2008-07-22 01:57:58 UTC

Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2008-07-22 05:41:11
project_key: SOA

Per this URL:
https://engineering.redhat.com/docbot/en-US/JBoss_SOA_Platform/4.2/html-single/SOA_ESB_Administrators_Guide/#id2649911

"1.3. JBossESB JMS Providers

The JBossESB supports a number of JMS providers. Currently we have successfully tested JBossMQ, ActiveMQ and Websphere MQ Series (version 5.3 and 6.0). For the SOA Platform JBossMQ is the recommended, tested, and supported JMS provider."

Shouldn't the above statement be changed to JBoss Messaging as recommended now vs. JBoss MQ?  I didn't scan the entire documentation for this bug (or would it be a task?), but my guess is that the docs need to be combed to fix this.

Comment 1 Mark Little 2008-07-22 09:41:11 UTC

As of the 4.3 release of ESB the docs no longer recommend JBossMQ. We should pick this fix up automatically.

Comment 2 Dana Mison 2008-08-01 01:37:33 UTC

updated in JBoss ESB 4.3 GA Administration Guide draft

https://engineering.redhat.com/docbot/en-US/JBoss_SOA_Platform/4.3/html-single/SOA_ESB_Administration_Guide/#JBossESB_JMS_Providers

Comment 3 David Ward 2008-08-01 01:46:38 UTC

Thanks Darrin, however there are other places in the docs that need updating.  For example, just scrolling down a bit on the same page:

"1.2.1. JBossMQ or JBossMessaging

JBossMQ is currently default JMS provider in JBossAS but you can also use JBoss Messaging. Instructions for installing JBoss Messaging can be found on the project website,"

...and then the instructions further down continue to assume JBoss MQ.  Unfortunately I do not have commit rights, so all I can do now is help by submitting JIRAs...

Comment 4 Dana Mison 2008-08-01 02:04:26 UTC

I beleive you should have commit rights assuming you are logged on with your kerberos credentials.  I'll email you seperately with the repo details

When you commit please put the JIRA reference in the comment so I can follow the changes.

Comment 5 Dana Mison 2008-08-12 04:57:37 UTC

To avoid problems keeping community & enterprise docs in sync please submit JIRAs for documentation issues.  Thanks for the offer though. :-)

I have applied your changes to the JBoss ESB Administration Guide for 4.3

Comment 6 Jiri Pechanec 2008-10-28 07:54:02 UTC

Verified in GA