Bug 739956

Summary: Message content-type is not set using python spout
Product: Red Hat Enterprise MRG Reporter: Petr Matousek <pematous>
Component: python-qpidAssignee: messaging-bugs <messaging-bugs>
Status: NEW --- QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: low Docs Contact:
Priority: low    
Version: DevelopmentCC: jross
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Petr Matousek 2011-09-20 14:38:43 UTC
Description of problem:

Message content-type property is not set using python spout. C++ and JMS clients sets the content-type on sending the message. All the clients shall behave the same way.

Version-Release number of selected component (if applicable):
python-qpid-0.10-1

How reproducible:
100%

Steps to Reproduce:
1. qpid-config add queue q
2. spout q "plain_text_message"
3. drain q
4. message property content-type is not set
  
Actual results:
Message content-type is not set

Expected results:
Appropriate content-type is set on sending the message with spout

Additional info: