hi again, it seems to me that there is a conceptual flaw in how sample 111 converts request/responses over HTTP to requests/responses over JMS: how are responses from the SimpleStockQuoteService sent back via JMS to synapse?
i understand the message flow in sample 111 as follows: 1. client sends SOAP/HTTP request for the getQuote operation to the synapse proxy. This is an in-out operation and the client actually waits synchronously for the response. 2. the synapse proxy accepts this request message and routes it to SimpleStockQuoteService via JMS by posting a JMS message on the SimpleStockQuoteService queue. 3. the SimpleStockQuoteService accepts the request and replies synchronously with a response. But where is that reponse sent to? Since this service is invoked through JMS in this scenario, i would expect the response message to be sent to a JMS queue - but where is that queue configured? 4. assuming that the reponse message was put on a JMS queue, synapse must now listen on that queue. This is for the out-rule of synapse. I don't see how/where i could tell synapse to listen on a particular JMS queue for response messages from a service. 5. assuming that the response message was received by synapse from that JMS queue, the synapse proxy then puts that message into the SOAP/HTTP response for the initial SOAP/HTTP request 6. client receives the SOAP/HTTP response for his initial request (synchronously, in this example). there seems to be a missing link here somewhere that handles the translation from *one* request/response pair in SOAP/HTTP to *two* queues (input and output) for the JMS transport. The root problem is that the SOAP operation invoked by the client is an in-out operation. I could imagine that the synapse proxy needs to inserts a WSA reply-to header with a JMS-address before sending the request to the SimpleStockQuoteService... please help me solve this mystery! ;-) kind regards, gerald -- http://www.gerald-loeffler.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
