DO NOT REPLY [Bug 16199] New: - response soap headers not passed to WSIF client

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16199>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16199

response soap headers not passed to WSIF client

           Summary: response soap headers not passed to WSIF client
           Product: Axis-WSIF
           Version: current (nightly)
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@xml.apache.org
        ReportedBy: antelder@apache.org


WSIF allows setting soap headers by setting an ArrayList of DOM Elements in the
context message. However when processing the response WISF does not put in
response soap header information back in the context. 

Note: Currently WSIF does no validation on these Elements or checking against
any soap header definitions in the WSDL. WSIF needs to fully implement this as
defined in the WSDL 1.1 spec - 3.7 soap:header and soap:headerfault. Thats a
bigger change   and its not completely clear how it should be done. This defect
is just to provider the means of returning any soap headers in the context message.