[
https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damitha Kumarage updated AXIS2C-1277:
-------------------------------------
Attachment: soap_header.c.diff
File attached has the desired solution. If there is no soap headers to be added
then serialized envelope don't have a empty soap header. In the server side
also it correctly handles when there is no soap header elemen present.
Can someone who is more familier with Axiom review this patch?
> Must use empty header in request
> --------------------------------
>
> Key: AXIS2C-1277
> URL: https://issues.apache.org/jira/browse/AXIS2C-1277
> Project: Axis2-C
> Issue Type: Bug
> Reporter: Ruth Struck
> Attachments: soap_header.c.diff
>
>
> Why must an empty </header> element be included in the SOAP request in order
> to use axis? I have two implementations of a web service, one is gsoap and
> the other is Axis2C - both have the same SOAP request - the gsoap
> implementation does not require the empty header element in the request, the
> Axis2C service does. How can I get around that requirement?
> The SOAP request:
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:ns1="http://localhost:80/axisae/aewebservices71.wsdl";>
> <SOAP-ENV:Body>
> <GetVersion xmlns="urn:aewebservices71" />
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
