2009/1/7 Asankha C. Perera <[email protected]>
> 1) Some HTTP/SOAP/POX client you have sends a request to a Synapse proxy > service > > Http Client -----(HTTP)-----> SynapseProxyService > > 2) SynapseProxyService posts it into a JMS Request Queue > > SynapseProxyService -----------------> JMS RequestQ > > 3) Some JMS service you have already written reads from the RequestQ and > does some thing, and writes back a response to another Queue > > JMS RequestQ --------------------> JMS Service --------------------> JMS > ResponseQ > > Note: As with standard JMS applications, the response posted to the > ResponseQ must have the correct correlation ID copied from the original > request > > 4) SynapseProxyService listens for JMS response message on ResponseQ, and > sends this back to the original HTTP/SOAP/POX client > > JMS ResponseQ ------------> SynapseProxyService > -----------(HTTP)----------> Http Client > > Is this your requirement? > > Yes, it's exactly what I need, but it could be done without "JMS Service" just to throw message from JMS RequestQ into JMS ResponseQ, and send it back via SynapseProxyService to Http Client. I've tried to run your sample, but still don't work is it only part of full length configuration (I assume yes because Response Q is nowhere defined). The most problematic for me is consuming from ResponseQueue in MyProxy, because I have no idea how to send JMS message back to proxy, if you use transports="http" in proxy there will be not queue named MyProxy, so what way MyProxy can consume from ResponseQueue it should have something defined to know what queue it should listen to, or Reply to should point to JNDI of proxy I think. I agree that it should be correlation between request and response (can you tell me just to be clear you think about JMSMessageId, or JMSCorrelationId?), and if it is setup I can rewrite it, so thanks for suggestion. If you can write some answers about my questions, I would be very gratefuly.
