You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Nikhil Thaker (JIRA)" <ji...@apache.org> on 2008/03/04 20:49:40 UTC
[jira] Created: (AXIS2-3568) WRONG SOAP-MUSTUNDERSTAND-HANDLING
WHEN USING JAX-WS HANDLER
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
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3568) Wrong SOAP MustUnderstand Handling
when using JAX-WS Handler
Posted by "Nikhil Thaker (JIRA)" <ji...@apache.org>.
[ 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.txt
Attached is the patch with all required changes for this JIRA.
> 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.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 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Work started: (AXIS2-3568) Wrong SOAP MustUnderstand
Handling when using JAX-WS Handler
Posted by "Nikhil Thaker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on AXIS2-3568 started by Nikhil Thaker.
> 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
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: (AXIS2-3568) Wrong SOAP MustUnderstand Handling when using JAX-WS
Handler....SEEING NPE!
Posted by R J Scheuerle Jr <sc...@us.ibm.com>.
yes indeed. thanks for the heads up.
Rich Scheuerle
IBM Web Services
Apache Axis2 (scheu@apache.org)
512-838-5115 (IBM TL 678-5115)
Davanum Srinivas <da...@gmail.com> wrote on 03/13/2008 08:48:35 PM:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Rich,
>
> It should be
>
> if(unprocessed == null || unprocessed.size() == 0){
>
> If you look at the context, if it is null or empty we should return.
>
> 104 : List<QName> unprocessed = (List)msgContext.
> getProperty(Constants.UNPROCESSED_HEADER_QNAMES);
> 105 : if(unprocessed == null || unprocessed.size()==0){
> 106 : if(log.isDebugEnabled()){
> 107 : log.debug("UNPROCESSED_HEADER_QNAMES not found.");
> 108 : }
> 109 : return;
> 110 : }
>
> thanks,
> dims
>
> R J Scheuerle Jr wrote:
> | I am seeing an NPE when running with this new code in the new
HandlerUtils
> | class.
> |
> | 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.
> |
> | Thanks
> |
> | Rich Scheuerle
> | IBM Web Services
> | Apache Axis2 (scheu@apache.org)
> | 512-838-5115 (IBM TL 678-5115)
> |
> |
> |
> | "Nikhil Thaker
> | (JIRA)"
> | <ji...@apache.org>
To
> | axis-dev@ws.apache.org
> | 03/13/2008 04:38
cc
> | PM
> |
Subject
> | [jira] Resolved: (AXIS2-3568)
Wrong
> | Please respond to SOAP MustUnderstand Handling
when
> | axis-dev@ws.apach using JAX-WS Handler
> | e.org
> |
> |
> |
> |
> |
> |
> |
> |
> |
> |
> | [
> | https://issues.apache.org/jira/browse/AXIS2-3568?page=com.
> atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> | ]
> |
> | Nikhil Thaker resolved AXIS2-3568.
> | ----------------------------------
> |
> | Resolution: Fixed
> |
> | Commited JIRA_3568_MustUnderstand_final.txt patch. This issue is now
> | resolved.
> |
> | revision # 636898.
> |
> |> 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.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
> | 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: axis-dev-unsubscribe@ws.apache.org
> | For additional commands, e-mail: axis-dev-help@ws.apache.org
> |
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFH2dlzgNg6eWEDv1kRArr3AKCfMOCBDJiuh4/qWSVdul2ebTZy+ACcCR7S
> cAi11m9cPAu9T8oSOjAOvnE=
> =xGIP
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
Re: (AXIS2-3568) Wrong SOAP MustUnderstand Handling when using JAX-WS
Handler....SEEING NPE!
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rich,
It should be
if(unprocessed == null || unprocessed.size() == 0){
If you look at the context, if it is null or empty we should return.
104 : List<QName> unprocessed = (List)msgContext.getProperty(Constants.UNPROCESSED_HEADER_QNAMES);
105 : if(unprocessed == null || unprocessed.size()==0){
106 : if(log.isDebugEnabled()){
107 : log.debug("UNPROCESSED_HEADER_QNAMES not found.");
108 : }
109 : return;
110 : }
thanks,
dims
R J Scheuerle Jr wrote:
| I am seeing an NPE when running with this new code in the new HandlerUtils
| class.
|
| 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.
|
| Thanks
|
| Rich Scheuerle
| IBM Web Services
| Apache Axis2 (scheu@apache.org)
| 512-838-5115 (IBM TL 678-5115)
|
|
|
| "Nikhil Thaker
| (JIRA)"
| <ji...@apache.org> To
| axis-dev@ws.apache.org
| 03/13/2008 04:38 cc
| PM
| Subject
| [jira] Resolved: (AXIS2-3568) Wrong
| Please respond to SOAP MustUnderstand Handling when
| axis-dev@ws.apach using JAX-WS Handler
| e.org
|
|
|
|
|
|
|
|
|
|
| [
| https://issues.apache.org/jira/browse/AXIS2-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
| ]
|
| Nikhil Thaker resolved AXIS2-3568.
| ----------------------------------
|
| Resolution: Fixed
|
| Commited JIRA_3568_MustUnderstand_final.txt patch. This issue is now
| resolved.
|
| revision # 636898.
|
|> 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.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
| 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: axis-dev-unsubscribe@ws.apache.org
| For additional commands, e-mail: axis-dev-help@ws.apache.org
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFH2dlzgNg6eWEDv1kRArr3AKCfMOCBDJiuh4/qWSVdul2ebTZy+ACcCR7S
cAi11m9cPAu9T8oSOjAOvnE=
=xGIP
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
(AXIS2-3568) Wrong SOAP MustUnderstand Handling when using JAX-WS Handler....SEEING
NPE!
Posted by R J Scheuerle Jr <sc...@us.ibm.com>.
I am seeing an NPE when running with this new code in the new HandlerUtils
class.
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.
Thanks
Rich Scheuerle
IBM Web Services
Apache Axis2 (scheu@apache.org)
512-838-5115 (IBM TL 678-5115)
"Nikhil Thaker
(JIRA)"
<ji...@apache.org> To
axis-dev@ws.apache.org
03/13/2008 04:38 cc
PM
Subject
[jira] Resolved: (AXIS2-3568) Wrong
Please respond to SOAP MustUnderstand Handling when
axis-dev@ws.apach using JAX-WS Handler
e.org
[
https://issues.apache.org/jira/browse/AXIS2-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Thaker resolved AXIS2-3568.
----------------------------------
Resolution: Fixed
Commited JIRA_3568_MustUnderstand_final.txt patch. This issue is now
resolved.
revision # 636898.
> 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.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
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-3568) Wrong SOAP MustUnderstand Handling
when using JAX-WS Handler
Posted by "Nikhil Thaker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikhil Thaker resolved AXIS2-3568.
----------------------------------
Resolution: Fixed
Commited JIRA_3568_MustUnderstand_final.txt patch. This issue is now resolved.
revision # 636898.
> 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.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 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3568) Wrong SOAP MustUnderstand Handling
when using JAX-WS Handler
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-3568:
------------------------------------
Summary: Wrong SOAP MustUnderstand Handling when using JAX-WS Handler (was: WRONG SOAP-MUSTUNDERSTAND-HANDLING WHEN USING JAX-WS HANDLER)
Fix subject..
> 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
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3568) Wrong SOAP MustUnderstand Handling
when using JAX-WS Handler
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-3568:
------------------------------------
Fix Version/s: 1.4
> 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
>
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3568) Wrong SOAP MustUnderstand Handling
when using JAX-WS Handler
Posted by "Nikhil Thaker (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Closed: (AXIS2-3568) Wrong SOAP MustUnderstand Handling when
using JAX-WS Handler
Posted by "Nikhil Thaker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nikhil Thaker closed AXIS2-3568.
--------------------------------
> 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.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 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3568) Wrong SOAP MustUnderstand Handling
when using JAX-WS Handler
Posted by "Nikhil Thaker (JIRA)" <ji...@apache.org>.
[ 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_final.txt
Added negative test for MU check in this patch.
> 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.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 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3568) Wrong SOAP MustUnderstand Handling
when using JAX-WS Handler
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576643#action_12576643 ]
Davanum Srinivas commented on AXIS2-3568:
-----------------------------------------
Nikhil,
We need this for 1.4 right?
thanks,
dims
> 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
>
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org