axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From R J Scheuerle Jr <>
Subject (AXIS2-3568) Wrong SOAP MustUnderstand Handling when using JAX-WS Handler....SEEING NPE!
Date Fri, 14 Mar 2008 01:00:19 GMT

I am seeing an NPE when running with this new code in the new HandlerUtils

if(unprocessed == null && unprocessed.size()>0){

should be

if(unprocessed == null || unprocessed.size()>0){

I am rerunning the tests with the change and will commit a little later
this evening.


Rich Scheuerle
IBM Web Services
Apache Axis2 (
512-838-5115  (IBM TL 678-5115)

             "Nikhil Thaker                                                
             <>                                          To 
             03/13/2008 04:38                                           cc 
                                       [jira] Resolved: (AXIS2-3568) Wrong 
             Please respond to         SOAP MustUnderstand Handling when   
             axis-dev@ws.apach         using JAX-WS Handler                


Nikhil Thaker resolved AXIS2-3568.

    Resolution: Fixed

Commited JIRA_3568_MustUnderstand_final.txt patch. This issue is now

revision # 636898.

> Wrong SOAP MustUnderstand Handling when using JAX-WS Handler
> ------------------------------------------------------------
>                 Key: AXIS2-3568
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Nikhil Thaker
>            Assignee: Nikhil Thaker
>             Fix For: 1.4
>         Attachments: JIRA_3568_MustUnderstand.txt,
JIRA_3568_MustUnderstand_final.txt, 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
> 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 ("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:
For additional commands, e-mail:

View raw message