Thanks for the responses everyone. I've tried the suggestions of adding an <enableAddressing/> element as a child of the <endpoint> element, this didnt appear to work.
I also tried adding this element, <property name="SOAP-Action" action="set" value="http://tempuri.org/IPointOfSale/RetrievePatientInfoWithOrders" scope="transport"/>, to the <inSequence> -- this also did not appear to work. In both cases, I received the same error that I previously did. Below is a soap envelope sent directly from axis2 w/o using synapse as a proxy. Looking at and the envelope sent by synapse, I think Asankha is probably correct about the http headers being the problem -- as you can see the http headers in the message sent by axis2 do not have the mismatches between the POST request header and the Host header that the synapse envelope did. The synapse envelope has the Host: header as localhost:8020 (this is where synapse is running) not sure why it would do this? I'm not certain what is causing the problem with the http headers or how to correct it? Thanks Steve Hall >From axis2 directly to the .net service POST /ScriptMedPOSBIOST/PointOfSaleService.svc HTTP/1.1 Content-Type: application/soap+xml; charset=UTF-8; action="http://tempuri.org/IPointOfSale/RetrievePatientInfoWithOrders" User-Agent: Axis2 Host: 10.1.90.54:1150 Transfer-Encoding: chunked <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"> <soapenv:Header> <wsa:To>http://10.1.90.54:1150/ScriptMedPOSBIOST/PointOfSaleService.svc</wsa:To> <wsa:MessageID>urn:uuid:3E9568CF21F353B8491225221280762</wsa:MessageID> <wsa:Action>http://tempuri.org/IPointOfSale/RetrievePatientInfoWithOrders</wsa:Action> </soapenv:Header> <soapenv:Body> <ns2:RetrievePatientInfoWithOrders xmlns:ns2="http://tempuri.org/"> <ns2:userId>TEST1</ns2:userId> <ns2:orderId>665700</ns2:orderId> <ns2:storeNumber>46</ns2:storeNumber> </ns2:RetrievePatientInfoWithOrders> </soapenv:Body> </soapenv:Envelope> >From synapse to the .net service: POST http://10.1.90.54:1150/ScriptMedPOSBIOST/PointOfSaleService.svc HTTP/1.1 Host: localhost:8280 Content-Type: application/soap+xml; charset=UTF-8; action="http://tempuri.org/IPointOfSale/RetrievePatientInfoWithOrders" Transfer-Encoding: chunked Connection: Keep-Alive User-Agent: Synapse-HttpComponents-NIO <?xml version="1.0" encoding="utf-8"?> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://www.w3.org/2005/08/addressing"> <soapenv:Header> <wsa:To>http://10.1.90.54:1150/ScriptMedPOSBIOST/PointOfSaleService.svc</wsa:To> <wsa:MessageID>urn:uuid:A87E61F1744D955E0F1224865751760</wsa:MessageID> <wsa:Action>http://tempuri.org/IPointOfSale/RetrievePatientInfoWithOrders</wsa:Action> </soapenv:Header> <soapenv:Body> <ns2:RetrievePatientInfoWithOrders xmlns:ns2="http://tempuri.org/"> <ns2:userId>TEST1</ns2:userId> <ns2:orderId>665700</ns2:orderId> <ns2:storeNumber>46</ns2:storeNumber> </ns2:RetrievePatientInfoWithOrders> </soapenv:Body> </soapenv:Envelope> ----- Original Message ---- From: Asankha C. Perera <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, October 27, 2008 9:13:14 PM Subject: Re: [synapse] new user having trouble with proxy example Hi Stephen > Below, I've included the soap envelope sent by axis2, the envelope then sent > by synapse, the fault returned by the .net service, the wsdl, the synapse > config, and the setUp method of a junit test where I configure axis2. I've > tried a number of different things with the axis2 ServiceClient config from > explicitly setting an action to adding proxy properties. > > The fault says I mismatch between the action in my header (not sure if thats > soap or http so i included both) but I don't see it? > Could you attach a trace of a successful call from any client to this service? This will help us pinpoint the problem much quicker.. also do you have a proxy service on your network.. The following (as sent by Synapse) is not correct either: POST http://10.1.90.54:1150/ScriptMedPOSBIOST/PointOfSaleService.svc HTTP/1.1 Host: localhost:8280 The "Host" header does not match the full URL provided in the POST, and .Net has been known to have a few issues around some subtle differences like these and the error its reporting has a chance to be misleading.. asankha
