Bug 1005757 - Wrong example code for subscribing to XML Exchange
Summary: Wrong example code for subscribing to XML Exchange
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference
Version: 2.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 2.5
: ---
Assignee: Joshua Wulf
QA Contact: Leonid Zhaldybin
URL:
Whiteboard:
Depends On: 1005750
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-09 10:44 UTC by Petr Matousek
Modified: 2014-11-09 22:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1005750
Environment:
Last Closed: 2014-05-30 04:45:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Matousek 2013-09-09 10:44:08 UTC
+++ This bug was initially created as a clone of Bug #1005750 +++

Description of problem:

4.10.4. Subscribe to the XML Exchange
Following two  lines shall be removed from the example code at the end of this chapter in order to show the proper xml exchange functionality. 

-  rx = ssn.receiver('myxmlq; {create: always, link: {x-bindings: [{exchange: myxml, key: weather, arguments: {xquery: "./weather"}}]}}')
-  print rxaddr

Explanation:
The properly defined example consumer using a specific xml filter (rx = ssn.receiver(rxaddr)) is overwritten with a consumer that matches all the messages whose body content has the root XML element '<weather>'. The definition is followed by an extra print that was probably used for debug purpose and was left in the code.

Version-Release number of selected component (if applicable):
Messaging Programming Reference (mrg-m-2.x) - Revision 2-34
Messaging Programming Reference (mrg-m-3.0) - Revision 0.0.0-1

How reproducible:
n/a

Steps to Reproduce:
n/a

Actual results:
Incorrect example code

Expected results:
functional example code

Additional info:

Comment 1 Petr Matousek 2013-09-09 10:46:15 UTC
Cloned for 2.3.x to highlight that this issue shall be fixed also in the MRG Messaging 2.x documentation.

Comment 3 Leonid Zhaldybin 2014-04-02 10:49:23 UTC
The example code has been fixed.

-> VERIFIED


Note You need to log in before you can comment on or make changes to this bug.