[jira] [Updated] (NIFI-5660) JMSPublisher should not set header properties directly in the message

["Joseph Witt (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Witt updated NIFI-5660:
------------------------------
    Fix Version/s: 1.9.1

> 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
>             Fix For: 1.10.0, 1.9.1
>
>          Time Spent: 20m
>  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)