You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Gardella Juan Pablo (Jira)" <ji...@apache.org> on 2020/06/19 12:31:00 UTC

[jira] [Updated] (NIFI-7564) Do not call Message setDestination on PublishJMS

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

Gardella Juan Pablo updated NIFI-7564:
--------------------------------------
    Issue Type: Improvement  (was: Bug)

> Do not call Message setDestination on PublishJMS
> ------------------------------------------------
>
>                 Key: NIFI-7564
>                 URL: https://issues.apache.org/jira/browse/NIFI-7564
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Gardella Juan Pablo
>            Priority: Minor
>
> According to [Message#setJMSDestination|https://docs.oracle.com/javaee/7/api/javax/jms/Message.html#setJMSDestination-javax.jms.Destination-] documentation, this method should not be called by clients, only by the providers:
> ??This method is for use by JMS providers only to set this field when a message is sent. This message cannot be used by clients to configure the destination of the message. This method is public to allow a JMS provider to set this field when sending a message whose implementation is not its own.??
> Notice by having a basic flow ConsumeJMS(destination=A) to PublishJMS(destination=B) it will be set the destination in the message to A, although that is not true. 
> It is better to do not set that value in the publish jms as that is actually handled by the JMS provider driver.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)