Good afternoon *,

I'm trying to get a web service proxy up and running, and I ran into some 
problems with this. This is my configuration:

<definitions xmlns="http://ws.apache.org/ns/synapse";>
    <proxy name="WS_Customer_Control">
        <target>
            <inSequence>
                <log level="trace"/>
                <send>
                    <endpoint>
                        <address 
uri="http://ws001/soap/v1/WS_Customer_Control"/>
                    </endpoint>
                </send>
            </inSequence>
            <outSequence>
                <send/>
            </outSequence>
        </target>
        <publishWSDL uri="http://ws001/soap/v1/WS_Customer_Control?wsdl"/>
    </proxy>
</definitions>

When I invoke a request on that service, it forwards that request 
(unmodified), but the receiving server runs into an error. Wireshark gave 
me a hint on this:

POST http://ws001/soap/v1/WS_Customer_Control HTTP/1.1
Host: localhost:8280
SOAPAction: ""
Accept: application/soap+xml, application/dime, multipart/related, text/*
Pragma: no-cache
Cache-Control: no-cache
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked
Connection: Keep-Alive
User-Agent: Synapse-HttpComponents-NIO

<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>..[original 
content]..]</soapenv:Envelope>

The target host (ws001) is running an apache server, which forwards the 
request to a Tomcat (4.1.36) instance, and this server seems to have this 
problem:

No Context configured to process this request</u></p><p><b>description</b> 
<u>The server encountered an internal error (No Context configured to 
process this request) that prevented it from fulfilling this request.

It seems to have problems with the fully qualified url in the POST request 
(overriding the dubious host header, via <property scope="transport" 
name="Host" value="ws001"> changes nothing). After patching 
Axis2HttpRequestHeader class in a way that a "POST 
/soap/v1/WS_Customer_Control HTTP/1.1" is sent, everything works just 
fine.

Is there any hidden setting which I overlooked that forces synapse to use 
the absolute path instead of the fully qualified url in this post 
requests?

kind regards,
Bertram Fey

-- 

Bertram Fey

Portale und Web-Technologie

ENTEGA Service GmbH
Landwehrstraße 55
64293 Darmstadt

Telefon: +49 (0)6151 970-2045
Telefax: +49 (0)6151 970-2289
E-Mail: [EMAIL PROTECTED]
Internet: http://www.entega-service.de



ENTEGA Service - ein Unternehmen der HEAG Südhessischen Energie AG (HSE) 
und der Stadtwerke Mainz AG
..........................................................................................
ENTEGA Service GmbH
Geschäftsführung:            
Dipl.-Ing. Johannes Brüssermann (Sprecher)
Dipl.-Kfm. Volker Abert

Sitz der Gesellschaft: Mainz
Registergericht: Amtsgericht Mainz HRB 3950

   

Reply via email to