[
https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019155#comment-13019155
]
Ivan commented on AXIS2-5001:
-----------------------------
Yes, I already mentioned it in the email posted in the user list, and I also
agree that it might not need to fix even violate with the spec. But from TCK
side, I saw the same case passed for RI JAX-WS implementation, and the reason
for it is that they always includes an empty header for the soap message. That
is why I hope to find another workaround solution for it (Add an empty header
too ?), or might be I could try to challenge those cases, which is a bit
difficult :-(
> 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]
