Joey Frazee created NIFI-2790:
Summary: Set JMS destination name on send/receive instead of using
the default destination
Project: Apache NiFi
Issue Type: Improvement
Reporter: Joey Frazee
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
This message was sent by Atlassian JIRA