[
https://issues.apache.org/jira/browse/AXIS2-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689027#action_12689027
]
amarnath commented on AXIS2-3813:
---------------------------------
I am getting the same issue with my customer application. Is there any work
around on this. Is this expected to be fixed in any future releases?
Environment: WebSphere Process Server 6.1 and Axis 1.3
> Axis2 1.2 service does not understand soapenv:mustUnderstand
> ------------------------------------------------------------
>
> Key: AXIS2-3813
> URL: https://issues.apache.org/jira/browse/AXIS2-3813
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: Axis2 1.2 Windows XP Axis2 service deployed on WebSphere
> Application Server v 6.1.0.15
> Reporter: Abhay
>
> When the soap request contains soapenv:mustUnderstand="1" (which means web
> service is bound to read the security attribute) then Axis2 service fails to
> read the security attribute. I have also found something interesting going on
> here when I pass the SOAP request with soapenv:MustUnderstand="1" then AXIS2
> service is able to read the message properly. The only difference between two
> calls is the use of 'm' or 'M' !!!!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
