Bug 1045411

Summary:	[RFE] allow setting all the message fields using the x-amqp- type syntax
Product:	Red Hat Enterprise MRG	Reporter:	Petr Matousek <pematous>
Component:	qpid-cpp	Assignee:	messaging-bugs <messaging-bugs>
Status:	NEW ---	QA Contact:	Messaging QE <messaging-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	Development	CC:	gsim, jross
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
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 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