[
https://issues.apache.org/jira/browse/NIFI-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643602#comment-16643602
]
ASF GitHub Bot commented on NIFI-5660:
--------------------------------------
GitHub user markobean opened a pull request:
https://github.com/apache/nifi/pull/3053
NIFI-5660: JMSPublisher should not set header properties directly in …
…the message
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] Is your initial contribution a single, squashed commit?
### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
Integration tests validated expected behavior.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markobean/nifi NIFI-5660
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/3053.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3053
----
commit b6e5ca9d44e54fd3fc2cdc40b4a21a1b6783a452
Author: Mark Bean <mark.o.bean@...>
Date: 2018-10-05T14:08:28Z
NIFI-5660: JMSPublisher should not set header properties directly in the
message
----
> 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
> Priority: Major
>
> 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)
