takes Parameter data from yarch streams and publishes it to hornetq address (reverse of ActiveMQPpProvider)
To avoid a ping-pong effect:
- it creates a queue with a filter on hornet side
- it remembers a thread local version of the tuple in transition on yarch side
address where all the Command Queues and command stationed in the Queues are registered there is also a queue
with the same name that can be browsed to get the initial list
Collect here scenarios and corresponding methods for sending/receiving data:
sendRequest via rpcProducer
- "method" name as property and parameters as a ProtoBuf message
- should automatically encode the replyTo address
sendReply via rpcProducer
- OK/NOK as property and return parameters as a ProtoBuf message
- should somehow correlate with the request TODO
executeRpc via rpcProducer/rpcConsumer
-sendRequest and wait for replay a configurable timeout
sendData via dataProducer
- one chunk in a stream of data.