[
https://issues.apache.org/jira/browse/NIFI-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774488#comment-16774488
]
ASF subversion and git services commented on NIFI-5660:
-------------------------------------------------------
Commit a0c28ee19e1b29b30e17946f074a01f94cfbc3c0 in nifi's branch
refs/heads/master from Mark Bean
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a0c28ee ]
NIFI-5660: JMSPublisher should set some header properties in JmsTemplate
instead of directly in the message
NIFI-5660: Added lines to integration test to verify these header properties
(added by Mike Moser)
Signed-off-by: Mike Moser <[email protected]>
This closes #3053
> JMSPublisher should not set header properties directly in the message
> ---------------------------------------------------------------------
>
> Key: NIFI-5660
> URL: https://issues.apache.org/jira/browse/NIFI-5660
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.7.1
> Reporter: Mark Bean
> Assignee: Mark Bean
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> JMS clients cannot set most header properties directly in the message, and
> they have to call other methods to change the default values. Most header
> properties are set indirectly when the provider code publishes a message. The
> defaults for QOS properties (delivery mode, expiration and priority) have to
> be changed by explicit calls to the Spring JMSTemplate class. The only header
> values that can be set directly by the client code are JMSReplyTo,
> JMSCorrelationID and JMSType.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
