[ 
https://issues.apache.org/jira/browse/AXIS2-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikhil Thaker updated AXIS2-3568:
---------------------------------

    Attachment: JIRA_3568_MustUnderstand_new.txt

Attached is the patch with changes to AxisEngine based on the solutions 
discussed on mailing list. Most of the changes  are included in 
AxisEngine.checkMustUnderstand() and introduction of new method 
isReceiverMustUnderstandProcessor().

Please review it and if you have any further recommendation please let me know. 
I will be attaching patch that accomodate AxisEngine changes in jaxws layer and 
also submit new test cases that indicate support of Handler.getHeader() 
function in jaxws module.

-Nikhil.

> Wrong SOAP MustUnderstand Handling when using JAX-WS Handler
> ------------------------------------------------------------
>
>                 Key: AXIS2-3568
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3568
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Nikhil Thaker
>            Assignee: Nikhil Thaker
>             Fix For: 1.4
>
>         Attachments: JIRA_3568_MustUnderstand_new.txt
>
>
> Implemented a simple JAX-WS service provider "DemoService" and a simple 
> JAX-WS SOAP handler "DemoHandler". DemoHandler was configured on 
> DemoService's handlerChain. The DemoHandler implementationcontains a 
> getHeaders() method specifying that it handles the "myheader" header in the 
> "http://demo/"; namespace.
> When sending the attached SOAP request everything works fine. The handler is 
> called and the server responds with an appropriate SOAP response. The request
> is almost the same request, with the  only difference that the mustUnderstand 
> attribute for the "myheader" header has been set to "1". When sending this 
> request, the
> server responds with a SOAP fault generated  Axis runtime: "Must Understand 
> check failed soap :
> {http://demo/}
> myheader"
> This behaviour is incorrect, It does not conform to the JAX-WS specification 
> JSR-224 v2.0. Chapter 10.2.1 ("SOAP mustUnderstand Processing") and chapter 
> 10.1.1.3 ("SOAP header") mandate that all headers specified by the getHeaders 
> method of a SOAPHandler must be considererd as "understood" by the JAX-WS 
> runtime.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to