Hi There,

 

I am trying to add a SOAP Header to a WSDL in AXIS2 version 1.4.1. 

 

When I do I see that after I give the WSDL to AXIS2 that it generates
two Request Messages, one that contains the message that I want to pass
into the operation, and the other that contains a message that I want to
have declared in the HEADER. The resulting WSDL is not WSDL1.1
compliant. 

 

Why does AXIS2 do this? Is there a way around this as SOAPUI for
instance gets confused when it sees this? Am I doing something wrong?

 

This is an example of what is happening. Anyone any ideas. 

 

This is my request. 

            <wsdl:message name="UpdateContactRequest">

                        <wsdl:part name="UpdateContactRequest"
element="scns:UpdateContactRequest">

                        </wsdl:part>

                        <wsdl:part name="authentication"
element="scns:authentication">

                        </wsdl:part>

            </wsdl:message>

 

But my message becomes this after AXIS2 gets the WSDL..

 

    <wsdl:message name="UpdateContactRequest">

        <wsdl:part name="UpdateContactRequest"
element="scns:UpdateContactRequest"/>

 

    </wsdl:message>

    <wsdl:message name="UpdateContactRequest">

        <wsdl:part name="authentication" element="scns:authentication"/>

    </wsdl:message>

 

This is my binding. 

 

            <wsdl:binding name="UpdateContactSoapBinding"
type="wsns:UpdateContactPortType">

                        <soap:binding style="document"

 
transport="http://schemas.xmlsoap.org/soap/http"; />

                        <wsdl:operation name="UpdateContact">

                                    <soap:operation

 
soapAction="http://UpdateContact/UpdateContactPortType/UpdateContactRequ
est" />

                                    <wsdl:input>

                                                <soap:body
parts="UpdateContactRequest" use="literal" />

                                                <soap:header
message="wsns:UpdateContactRequest" part="authentication"

 
use="literal">

                                                </soap:header>

                                    </wsdl:input>

                                    <wsdl:output>

                                                <soap:body use="literal"
/>

                                    </wsdl:output>

                        </wsdl:operation>

            </wsdl:binding>

 

 

The binding changes also to.... 

 

            <wsdl:binding name="UpdateContactSoapBinding"
type="wsns:UpdateContactPortType">

                        <soap:binding style="document"

 
transport="http://schemas.xmlsoap.org/soap/http"; />

                        <wsdl:operation name="UpdateContact">

                                    <soap:operation

 
soapAction="http://UpdateContact/UpdateContactPortType/UpdateContactRequ
est" />

                                    <wsdl:input>

                                                <soap:body
parts="UpdateContactRequest" use="literal" />

                                                <soap12:header
message="wsns:UpdateContactRequest" part="authentication"
use="literal"/>

                                    </wsdl:input>

                                    <wsdl:output>

                                                <soap:body use="literal"
/>

                                    </wsdl:output>

                        </wsdl:operation>

            </wsdl:binding>

 

Any ideas.

 



"Misys" is the trade name for Misys plc (registered in England and Wales). 
Registration Number: 01360027. Registered office: One Kingdom Street, London W2 
6BL, United Kingdom. For a list of Misys group operating companies please go to 
http://www.misys.com/corp/About_Us/misys_operating_companies.html. This email 
and any attachments have been scanned for known viruses using multiple 
scanners. This email message is intended for the named recipient only. It may 
be privileged and/or confidential. If you are not the named recipient of this 
email please notify us immediately and do not copy it or use it for any 
purpose, nor disclose its contents to any other person. This email does not 
constitute the commencement of legal relations between you and Misys plc. 
Please refer to the executed contract between you and the relevant member of 
the Misys group for the identity of the contracting party with which you are 
dealing. 

Reply via email to