Bug 779884 (SOA-2243) - Remove jbmq-queue-service.xml files from quickstarts
Summary: Remove jbmq-queue-service.xml files from quickstarts
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2243
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 CP04 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-27 08:34 UTC by Martin Weiler
Modified: 2011-02-11 04:28 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 779885 (view as bug list)
Environment:
Last Closed: 2011-02-11 04:28:25 UTC
Type: Task

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-2243 0 None None None Never

Description Martin Weiler 2010-08-27 08:34:05 UTC 
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000003hjIl
project_key: SOA

The queue definition files for the legacy JBoss MQ should be removed from the quickstarts to avoid confusion.
Comment 1 Anne-Louise Tangring 2010-09-10 18:57:42 UTC 
This is a candidate for SOA 5.1.0
Comment 2 Kevin Conner 2010-09-22 04:17:14 UTC 
This should be handled by a platform build step, simply excluding the service.xml from the quickstarts.
Comment 3 trev 2010-10-25 15:58:45 UTC 
Committed revision 7088
Comment 5 Dana Mison 2011-01-05 00:14:43 UTC 
Writer: Added: dlesage
Comment 6 David Le Sage 2011-02-11 04:26:35 UTC 
Temporarily reopening to update release note info.
Comment 7 David Le Sage 2011-02-11 04:28:14 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2243

The queue definition files pertaining to  legacy JBoss message queuing have been removed from the quick starts. This has been done so as to avoid potential user confusion.
Note You need to log in before you can comment on or make changes to this bug.