Bug 768364 - BURL URLs must be prefixed with 'BURL:' string in example config file
Summary: BURL URLs must be prefixed with 'BURL:' string in example config file
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-jca
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: 2.1.2
: ---
Assignee: Weston M. Price
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-16 13:09 UTC by Jiri Pechanec
Modified: 2016-02-22 00:59 UTC (History)
3 users (show)

Fixed In Version: qpid-jca-0.14-3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-07 17:42:46 UTC
Target Upstream Version:

Attachments (Terms of Use)
Simple patch to prepend BURL: to destinationAddress string in example config file (1.91 KB, application/octet-stream)
2012-01-05 13:24 UTC, Weston M. Price 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jiri Pechanec 2011-12-16 13:09:18 UTC 
The config properties in qpid-jca-example-properties.xml are not prefixed and examples fails if this naming is in use.
Comment 1 Weston M. Price 2011-12-28 15:20:26 UTC 
I am not sure why this was filed as a blocker. This issue only effects the example files and should not impede in testing in any way. By default we use ADDR syntax, to use the older BURL syntax, destination strings simply need to be prefixed with BURL:

Since we don't encourage the use of BURL, this string was simply included in the examples for backwards compatibility. 

The blocker flag should be removed from this issue.
Comment 2 Weston M. Price 2012-01-05 13:24:43 UTC 
Created attachment 550900 [details]
Simple patch to prepend BURL: to destinationAddress string in example config file
Comment 3 Jiri Pechanec 2012-01-17 12:02:27 UTC 
Verified in 0.14-4
Note You need to log in before you can comment on or make changes to this bug.