[
https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030517#comment-13030517
]
Andreas Veithen commented on AXIS2-5001:
----------------------------------------
That sounds like a workaround that doesn't eliminate the root cause. Very
likely, the presence of the empty header is required by some other part of the
SAAJ or JAX-WS spec to which Axis2 doesn't comply. If this is the case, then we
need to figure out which requirement is violated and fix it.
Again, unless we get a test case that reproduces the actual issue (or at least
a description of what the TCK test attempts to do) we will not be able to
investigate this.
> SOAPMessage.getSOAPHeaders() return null while no headers in the soap envelope
> ------------------------------------------------------------------------------
>
> Key: AXIS2-5001
> URL: https://issues.apache.org/jira/browse/AXIS2-5001
> Project: Axis2
> Issue Type: Bug
> Components: saaj
> Affects Versions: 1.5.4
> Reporter: Ivan
>
> Per Java doc, SOAPMessage.getSOAPHeaders() should throw SOAPException while
> no header exists in the soap message, while it returns null in current
> axis2-saaj implementation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
