Hi Tanmay, You cannot put multiple endpoints within a send mediator, instead you will need to use three endpoints within three send mediators. I think it is better to clone the message before sending the responses, because otherwise the message might get corrupted.
So the effective configuration of the sending three responses in the outSequence would be something like following; <clone> <target><endpoint .......[SampleQ2]/></target> <target><endpoint .......[SampleQ3]/></target> <target><endpoint .......[SampleQ4]/></target> </clone> At the same time I saw you wrapped the xslt mediator with an out mediator which is of no use because the out mediator is just a filter to filter the response messages and inside outSequence you will be having only responses. So the out mediator is redundant. Hope this will help you.... Thanks, Ruwan On 6/19/08, tsaha <[EMAIL PROTECTED]> wrote: > > Hi Asankha/Ruwan: > > One of our business requirements is to send response back to multiple > endponits. I have configured the following proxy to Listen from SampleQ1 and > reply back to SampleQ2, SampleQ3 and SampleQ4. But it is sending the > response back to SampleQ2. Can you pl tell me why it is not working > > -Thanks > tanmay > > <definitions xmlns="http://ws.apache.org/ns/synapse";> > > <!-- define the request processing XSLT resource as a static URL source --> > <localEntry key="xslt-key-req" > src="file:repository/conf/sample/resources/transform/echo_transform.xslt"/> > > <proxy name="echoProxy" transports="jms"> > <target> > > <endpoint> > <address uri="http://ps-tsaha:8082/EJBWebService/EchoBean"/> > </endpoint> > > <outSequence> > > <log level="full"/> > <out> > <xslt key="xslt-key-req"/> > </out> > > > <send> > > <endpoint> > <address > uri="jms:/SampleQ2?transport.jms.ConnectionFactoryJNDIName=SonicQueueConnectionFactory&transport.jms.DestinationType=queue&java.naming.provider.url=tcp://localhost:2506&java.naming.factory.initial=com.sonicsw.jndi.mfcontext.MFContextFactory&java.naming.security.principal=Administrator&java.naming.security.credentials=Administrator" > /> > </endpoint> > > <endpoint> > <address > uri="jms:/SampleQ4?transport.jms.ConnectionFactoryJNDIName=SonicQueueConnectionFactory&transport.jms.DestinationType=queue&java.naming.provider.url=tcp://localhost:2506&java.naming.factory.initial=com.sonicsw.jndi.mfcontext.MFContextFactory&java.naming.security.principal=Administrator&java.naming.security.credentials=Administrator" > /> > </endpoint> > > <endpoint> > <address > uri="jms:/SampleQ3?transport.jms.ConnectionFactoryJNDIName=SonicQueueConnectionFactory&transport.jms.DestinationType=queue&java.naming.provider.url=tcp://localhost:2506&java.naming.factory.initial=com.sonicsw.jndi.mfcontext.MFContextFactory&java.naming.security.principal=Administrator&java.naming.security.credentials=Administrator" > /> > </endpoint> > > </send> > > > > </outSequence> > </target> > > <parameter > name="transport.jms.ConnectionFactory">myQueueConnectionFactory</parameter> > <parameter name="transport.jms.Destination">SampleQ1</parameter> > <parameter name="transport.jms.DestinationType">queue</parameter> > > <publishWSDL > uri="file:repository/conf/sample/resources/proxy/echo_proxy.wsdl"/> > </proxy> > > </definitions> > -- > View this message in context: > http://www.nabble.com/Not-able-to-send-response-back-to-multiple-endpoints-tp17991633p17991633.html > Sent from the Synapse - User mailing list archive at Nabble.com. > > -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/
