[
https://issues.apache.org/jira/browse/NIFI-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15506704#comment-15506704
]
ASF subversion and git services commented on NIFI-2790:
-------------------------------------------------------
Commit c2e98f96ebe30a6a8c919ed8a747a5829f5dea0f in nifi's branch refs/heads/0.x
from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=c2e98f9 ]
NIFI-2789, NIFI-2790 - polishing
> 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: Joey Frazee
> 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)
