What is your client?
Samisa...
Nandika Jayawardana wrote:
Axis2/C is able to recognise both SOAP1.1 and SOAP1.2 namespaces. One
posibility is that, your message's content type and soap namespace
does not match and hence the error.
If the message is of type soap11, it should have content type text/xml
while if the message is soap1.2 it should have content type
application/soap+xml.
Regards
Nandika
On Tue, Dec 30, 2008 at 8:19 PM, Baxi, Rinilkumar (TCS)
<[email protected] <mailto:[email protected]>> wrote:
Hello,
I am working with Axis2/C and have been trying to invoke a
service using a client that sends SOAP 1.1 messages. On each try,
the Axis responds with 500 Internal Server Error.
On debugging, I found that Axis sets the error in the file
soapbuilder.c. It compares the incoming SOAP namespace with a SOAP
1.2 namespace. On a mismatch, it frees the soap builder and sets
the error.
How can I make it work with SOAP 1.1 clients? How will it
impact if I let Axis go ahead even for a SOAP 1.1 message? Will
such a code create problems further down the line?
Thanks,
Rinil
--
http://nandikajayawardana.blogspot.com/
WSO2 Inc: http://www.wso2.com
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.10.1/1868 - Release Date: 12/29/2008 10:48 AM
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
