Bug 636262 - QMF: method call arguments containing maps fail to pass boolean values.
Summary: QMF: method call arguments containing maps fail to pass boolean values.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-qmf
Version: beta
Hardware: All
OS: Linux
high
high
Target Milestone: 1.3
: ---
Assignee: Ken Giusti
QA Contact: Frantisek Reznicek
URL:
Whiteboard:
Depends On:
Blocks: 635979
TreeView+ depends on / blocked
 
Reported: 2010-09-21 19:09 UTC by Ken Giusti
Modified: 2015-11-16 01:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-20 11:29:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ken Giusti 2010-09-21 19:09:12 UTC
Description of problem:

Passing a method call an argument that is a map which contains native boolean values does not get sent to the agent.   The boolean values drop out.


Version-Release number of selected component (if applicable):


How reproducible:

100% using the wrapped python console vs. wrapped ruby agent.

Steps to Reproduce:
1.  define a method call that takes a map argument.
2.  Create a map with a boolean value:  eg {"tag": False}
3.  Call the method with the map argument
  
Actual results:

The map as received on the agent is empty {}


Expected results:

The map should contain {"tag": False}

Additional info:

Comment 3 Frantisek Reznicek 2010-09-27 13:20:09 UTC
The issue has been fixed, tested on RHEL 5.5 (agent + console) / 4.8 (python console only) i386 / x86_64 on packages:

python-qmf-0.7.946106-13.el5
python-qpid-0.7.946106-14.el5
python-saslwrapper-0.1.934605-2.el5
qmf-0.7.946106-17.el5
qmf-devel-0.7.946106-17.el5
qpid-cpp-*-0.7.946106-17.el5
qpid-dotnet-0.4.738274-2.el5
qpid-java-*-0.7.946106-10.el5
qpid-tools-0.7.946106-11.el5
ruby-qmf-0.7.946106-17.el5
ruby-qpid-0.7.946106-2.el5
ruby-saslwrapper-0.1.934605-2.el5
saslwrapper-0.1.934605-2.el5
saslwrapper-devel-0.1.934605-2.el5

-> VERIFIED


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