Hide Forgot
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.
As of the 4.3 release of ESB the docs no longer recommend JBossMQ. We should pick this fix up automatically.
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
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...
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.
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
Verified in GA