Naidoo, R. - SPLXE wrote:

Hi all,
   I have the following binding in my wsdl :
        <binding name="MySoapBinding" type="curr:Availability">
                <soap:binding style="document"
transport="http://my.com/custom/transport/"/>
                <operation name="getAvailability">
                        <soap:operation soapAction='http://my.com/blabla'/>
                        <input>
                                <soap:body use="literal"/>
                                 <soap:header message="curr:HeaderMsg"
part="UserID" use="literal"/>
                                 <soap:header message="curr:HeaderMsg"
part="Domain" use="literal"/>
                        </input>
                        <output>
                                <soap:body use="literal"/>duplicated
extensibility element
                        </output>
                </operation>
        </binding>

I am a bit uncertain whether I can define mutiple soap headers as
described above. I looked at the wsdl spec, and that seems to indicate that there can be
multiple headers.
<soap:header message="qname" part="nmtoken"
use="literal|encoded"
encodingStyle="uri-list"? namespace="uri"?>*
<soap:headerfault message="qname" part="nmtoken"
use="literal|encoded"
encodingStyle="uri-list"?
namespace="uri"?/>*
<soap:header>


   The reason for my uncertainty is as a result of the Apache AXIS provider
for WSIF. The provider complains of "duplicated extensibility element" when
trying to execute.

On closer investigation, I saw that the WSIFOperation_ApacheAxis class
is written to only handle a single <soap:header> and <soap:headerfault>
element.
Is this a bug? Would I be correct to change this class to handle
mulitple headers and multiple header faults for each header.


hi Ravan

i think it is a bug and if you add this to bugzilla and attach patch then i will look to apply it to codebase.

thanks,

alek

--
The best way to predict the future is to invent it - Alan Kay





Reply via email to