Hi Srinivas, Once the message is dispatched to Synapse you can not use just the send mediator unless you are specifying in the client that you are talking to this service while you use synapse as the proxy. In which case you need to define the full endpoint and use that to send the messages.
For example; <send><endpoint><address uri="http://<ipaddress>/service/MyService"/></endpoint></send> If not, you can use the header mediator to set the To header and then use the send mediator. <header name="To" value="http://<ipaddress>/service/MyService"/> <send/> This header value can also be dynamic using the expression attribute rather than the value attribute. Please have a look at the synapse samples for more information at [1] [1] - http://synapse.apache.org/Synapse_Samples.html Thanks, Ruwan On Mon, Mar 3, 2008 at 9:57 PM, Asankha C. Perera <[EMAIL PROTECTED]> wrote: > Hi Srinivas > > The issue I am facing is that the request sent to the destination > service is of the form > > > > POST http://<ipaddress>/service/MyService HTTP/1.0 > > > > instead of > > > > POST /service/MyService HTTP/1.0 > > > > and this is returning a 404. I am unable to figure out how to make this > work. > > > How did you view what was being sent vs what you require? was it through > TCPMon? (Since by default Synapse would use HTTP 1.1) Having the full > URL of a service instead of just the path is not a problem at all - > unless Synpase is trying to connect on a different IP - and your Axis2 > accepts connections on something else? > > Can you share any logs/traces for me to analyze the actual problem > > asankha > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
