Bug 1045411 - [RFE] allow setting all the message fields using the x-amqp- type syntax
Summary: [RFE] allow setting all the message fields using the x-amqp- type syntax
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: Messaging QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-20 11:23 UTC by Petr Matousek
Modified: 2019-02-08 14:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Bugzilla 975444 None None None Never

Internal Links: 975444

Description Petr Matousek 2013-12-20 11:23:00 UTC
Description of problem:

Due to the support for all amqp1.0 properties/headers, following new special properties were added:
x-amqp-first-acquirer, x-amqp-delivery-count, x-amqp-to, x-amqp-absolute-expiry-time, x-amqp-creation-time, x-amqp-group-id, x-amqp-qroup-sequence, 
x-amqp-reply-to-group-id

These fields do not have explicit accessors, so these fields must be set different way than the already existing ones. It would make sense to have unified way for setting the hearders/properties.
 
It would be reasonable to allow setting all the fields using the x-amqp- type syntax (e.f. x-amqp-subject etc) in addition to the existing explicit accessors.
At least for amqp1.0 defined headers/properties.

Version-Release number of selected component (if applicable):
qpid-cpp-*-0.22-29.el6

Actual results:
x-amqp-<property> available only for subset of message fields

Expected results:
unified way for setting all message headers/properties


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