Hi,
}
// OVERRIDE USER SPECIFED SETTINGS FOR 2 Content-types
axisConfig.addMessageBuilder("application/xml", new
ApplicationXMLBuilder());
axisConfig.addMessageBuilder("application/x-www-form-urlencoded",
new XFormURLEncodedBuilder());
AFAIKS this is already fixed in the trunk and will be available in the
1.3 release..
I'm not sure I follow you comments about SOAPAction Header.
Please use a message sniffing program like tcpmon
(ws.apache.org/commons/tcpmon) to capture the messages together with
the http headers...
Here's what a
typical SOAP request would look like:
<SoapEnvelope:Envelope
xmlns:SoapEnvelope="http://schemas.xmlsoap.org/soap/envelope/";>
<SoapEnvelope:Body>
<getCustomer>
<cust-id>2276772</cust-id>
</getCustomer>
</SoapEnvelope:Body>
</SoapEnvelope:Envelope>
By looking at the SOAP namespace you are using SOAP1.1... With SOAP1.1
you are required to have the SOAPAction http header...
If possible a quick and easy fix for this would be to use SOAP1.2...
Thanks,
Thilina
--
View this message in context:
http://www.nabble.com/text-xml-to-application-xml-trouble-tf3974013.html#a11289868
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
