I have a requirement to send messages to a SonicMQ queue as response to an earlier incoming message. The pattern I'm implementing is the EIP "Smart proxy" pattern (http://www.eaipatterns.com/SmartProxy.html) meaning that I have to respond dynamically to the consumer based on the queuename that he provided in the replyTo header. This is done asynchronously so my request and response flows are not coupled.
Now, my problem is that the replyTo name is the actual physical name, not the JNDI reference. I store the replyTo name during the request flow, to later pick it up based on correlation in the response flow. The integration product my client is using is the Websphere Message Broker, and it requires physical destinations to have a URL format if you dont want to look it up against JNDI.
Using Websphere MQ this physical URL would be i.e. queue://MYQUEUE, but the same type of URL is not supported by Sonic.
Does anyone know if Sonic has the same concept of a URL? I've tried integrating with ActiveMQ earlier and it had the same feature as WMQ. Their queues would be i.e. queue://dynamicQueue/MYQUEUE
Now, my problem is that the replyTo name is the actual physical name, not the JNDI reference. I store the replyTo name during the request flow, to later pick it up based on correlation in the response flow. The integration product my client is using is the Websphere Message Broker, and it requires physical destinations to have a URL format if you dont want to look it up against JNDI.
Using Websphere MQ this physical URL would be i.e. queue://MYQUEUE, but the same type of URL is not supported by Sonic.
Does anyone know if Sonic has the same concept of a URL? I've tried integrating with ActiveMQ earlier and it had the same feature as WMQ. Their queues would be i.e. queue://dynamicQueue/MYQUEUE