Bug 739956 - Message content-type is not set using python spout
Summary: Message content-type is not set using python spout
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: python-qpid
Version: Development
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-20 14:38 UTC by Petr Matousek
Modified: 2025-02-10 03:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:14:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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:
Comment 1 Red Hat Bugzilla 2025-02-10 03:14:14 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.