axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Updated: (AXIS2-3568) Wrong SOAP MustUnderstand Handling when using JAX-WS Handler
Date Sat, 08 Mar 2008 22:55:49 GMT


Davanum Srinivas updated AXIS2-3568:

    Fix Version/s: 1.4

> 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
> 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/"
> 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 ("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