Hi Ruwan and Asankha,
Thanks a lot for the response.
> 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?I got this information from the access
> log of the destination server. In the deployment that I have done, Synapse is
> trying to connect on a different IP.>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/>I did try both these methods, in either case, Axis2HttpRequest seems to
>be sending the request using the following code
httpRequest = new BasicHttpEntityEnclosingRequest(
"POST", epr.getAddress(), HttpVersion.HTTP_1_0);and
epr.getAddress() would end up returning the entire URL string and not just the
URL.getFile(). I did try to change this but I ended up having 500 errors on the
destination server.
I forced HTTP/1.0 because the server was returning a 100 Continue for HTTP/1.1
At this point I felt I am totally off track from what should have been the way
of configuring synapse. I did try the examples and they seemed to work fine,
but this scenario seems to have left me exhausted.
Once again thank you very much for the response. Please let me know if my
approach makes sense.
Thanks
Srinivas Rampalli
DISCLAIMER: This e-mail and any attachments are intended only for the
individual or company to which it is addressed and may contain information
which is privileged, proprietary, confidential and prohibited from disclosure
or unauthorized use under applicable law. If you are not the intended recipient
of this e-mail, you are hereby notified that any use, dissemination, or copying
of this e-mail or the information contained in this e-mail is strictly
prohibited by the sender. If you have received this transmission in error,
please return the material received to the sender and delete all copies from
your system.
