Multiple soap:header and soap:headerfault elements not accepted by
WSIFOperation_ApacheAxis.
--------------------------------------------------------------------------------------------
Key: WSIF-74
URL: http://issues.apache.org/jira/browse/WSIF-74
Project: Axis-WSIF
Type: Bug
Components: Basic Architecture
Versions: 2.0
Reporter: Rhett DeWall
WSDL 1.1 states that multiple soap:header and soap:headerfault elements are
valid; however, WSIFOperation_ApacheAxis.java only allows one per operation.
WSDL 1.1 excerpt listed below:
------------------------
<definitions .... >
<binding .... >
<operation .... >
<input>
<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>
</input>
<output>
<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>
</output>
</operation>
</binding>
</definitions>
------------------------
A fix is attached whereby lines 473 and 496 have been changed to call
getExtElems() versus getExtElem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
