Bug 778339 (SOA-824) - Admin Guide incorrectly includes activeMQ & OracleAQ as supported
Summary: Admin Guide incorrectly includes activeMQ & OracleAQ as supported
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-824
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.3 IR1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CR1
Assignee: Dana Mison
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-24 00:11 UTC by Dana Mison
Modified: 2008-10-20 12:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-20 12:02:37 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-824 0 None None None Never

Description Dana Mison 2008-09-24 00:11:35 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
Date of First Response: 2008-10-20 08:02:37
project_key: SOA

The SOA 4.3 Administration Guide contains configuration information & advice on Apache ActiveMQ & OracleAQ but makes no reference to the fact that both of those JMS implementations are untested & unsupported.  This information needs to be included.
Comment 1 Dana Mison 2008-09-24 00:13:38 UTC 
Updated contented added to 4.3 admin guide:

"The JBoss Enterprise SOA Platform currently supports JBoss Messaging, IBM Websphere MQ Series (version 5.3 and 6.0) and Tibco EMS as Java Message Service (JMS) providers.

We recommend JBoss Messaging and it is included with the default configuration.

Any JSR-914 (http://jcp.org/en/jsr/detail?id=914) compliant JMS implementation should also work such as Apache ActiveMQ and OracleAQ.  However these JMS providers have not been tested and are not supported at this time.  If you wish to test another JMS provider you should consult that vendor's documentation. "

The config information for each remains but a note is added that they are unsupported.
Comment 2 Jiri Pechanec 2008-10-20 12:02:37 UTC 
Verified in CR1
Note You need to log in before you can comment on or make changes to this bug.