Are you using WS-Addressing (the successor of WS-Routing)?
Or are you doing it directly...?
Trace the output and see the envelope generated by your middle-man.

Signature
Happy Hacking,
Gaurav Vaish | http://www.mastergaurav.com
http://www.edujinionline.com
http://articles.edujinionline.com/webservices
-------------------
> Hi All,
>
[quoted text clipped - 13 lines]
>
> Thanks,
Anbu - 29 Sep 2006 09:38 GMT
Gaurav,
Thanks for your reply.
The scenario would be a plain, in which I'm sending a request to
another web service which has to talk to another web service.
The flow is like this, WS1->WS2->WS3->WS4 and if the WS4 returns any
error, it has to be returned to WS1 through the same path. For sending
the messages I'm using SoapEnvelopes (part of WSE 3.0 requirements)
The problem is WS1 and WS4 are not WSE 3.0 services, but other two are.
The interation between WS2 and WS3 are through WSE 3.0 (here i traced
the output files. Error messages are forwarded as SoapFault).
But when i transmit the same message from WS2 to WS1 (by soapenvelope
or throwing exception) causes HttpError 500. Though it internally holds
the SoapEnvelope in the WebException's Response Object, I'm interested
in Http Header (which holds the HTTP Status Codes).
WS1 & WS4 may not be .NET web services or clients.
Thanks,