Toivo,
You're absolution right - this is very much an oversight, I think.
Typically, when I've used JMS processors I've been using GetJMS or PutJMS, but
I've not used GetJMS -> (something else) -> PutJMS.
PutJMS really should allow the Expression Language to be used for the
Destination. This would allow you to use the value '${jms.JMSReplyTo}' but
unfortunately the property doesn't currently support the Expression Language. I
have created a ticket (NIFI-610) to address this.
Thanks
-Mark
----------------------------------------
> Date: Sun, 17 May 2015 03:40:37 -0700
> From: [email protected]
> To: [email protected]
> Subject: Request response using JMS and JMSReplyTo
>
> 1. External client send request
>
> 2. GetJMS* processor receive request, store JMSReplyTo value
> if (message.getJMSReplyTo() != null) {
> attributes.put(ATTRIBUTE_PREFIX + JMS_REPLY_TO,
> message.getJMSReplyTo().toString());}
>
> 3. Next processors processes request and create response
>
> 4. And finally PutJMS should send response back to channel specified by
> JMSReplyTo
> But it seems PutJMS is not using JMSReplyTo, instead DESTINATION_NAME
> property value is used.
>
> Did I misunderstood something?
>
> Often response is expected to be in JMSReplyTo channel.
>
> Thanks
> Toivo
>
>
>
>
> --
> View this message in context:
> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/Request-response-using-JMS-and-JMSReplyTo-tp1557.html
> Sent from the Apache NiFi (incubating) Developer List mailing list archive at
> Nabble.com.
