[ 
https://issues.apache.org/jira/browse/NIFI-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503839#comment-15503839
 ] 

ASF GitHub Bot commented on NIFI-2790:
--------------------------------------

GitHub user jfrazee opened a pull request:

    https://github.com/apache/nifi/pull/1027

    NIFI-2790 Set JMS destination name on send/receive instead of using the 
default destination

    Note: This was branched off of NIFI-2789 / #1026.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jfrazee/nifi NIFI-2790

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1027.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 #1027
    
----
commit d59b4338a838dff88c66ff86ea377071cf981765
Author: Joey Frazee <joey.fra...@icloud.com>
Date:   2016-09-19T13:18:30Z

    Read JMS properties and add to FlowFile attributes in ConsumeJMS

commit 621fec64bd6ffbe7aefffcfd005421a6515c8ff2
Author: Joey Frazee <joey.fra...@icloud.com>
Date:   2016-09-19T14:49:07Z

    Remove unused assertEquals import

commit 1c76e22b06bd999496e19cd05d08db50660c1652
Author: Joey Frazee <joey.fra...@icloud.com>
Date:   2016-09-19T15:50:59Z

    Move destination from default to send/receive to support EL better

----


> Set JMS destination name on send/receive instead of using the default 
> destination
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-2790
>                 URL: https://issues.apache.org/jira/browse/NIFI-2790
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Joey Frazee
>            Assignee: Oleg Zhurakousky
>            Priority: Minor
>             Fix For: 1.1.0
>
>
> ConsumeJMS and PublishJMS currently pull their destination name from the 
> default JMS destination (setDefaultDestinationName() on the JmsTemplate). The 
> effect this has is that attribute expressions are evaluated with respect to 
> the context only and not the FlowFile, so expression language support really 
> only extends to EL functions and variables from the variable registry.
> This doesn't have a big impact on ConsumeJMS since it doesn't take input, but 
> it means that destinations can be set at runtime in PublishJMS.
> The JmsTemplate send() and receive() can take the destination name as an 
> argument though, so these method variants should be used so EL support is 
> fully enabled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to