search

javaee / metro-wsit

https://javaee.github.io/metro-wsit/
Other
9 stars 24 forks source link

WSA interop test 1147 fails(S->MS). Incorrect Fault thrown #287

Closed glassfishrobot closed 17 years ago

glassfishrobot commented 17 years ago

WSA interop test 1147 fails in Tango->Indigo mode.

A Tango client sends a request[1] with no wsa:Action header, and expects a "MessageAddressingHeaderRequired" fault. But the MS service is sending an "ActionMismatch" fault[2] with faultstring-

" The SOAP action specified on the message, '', does not match the HTTP SOAP Action, '' "

This Looks like an Indigo side issue.

============================================ [1] Request: <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">

[http://yinyang.india.sun.com/WSAddressingCR_Service_WCF/WSAddressing10.svc/Soap11](http://yinyang.india.sun.com/WSAddressingCR_Service_WCF/WSAddressing10.svc/Soap11) uuid:a6d1d662-12dd-46a8-a592-e36b51c1ef85 [http://www.w3.org/2005/08/addressing/anonymous](http://www.w3.org/2005/08/addressing/anonymous) test1147 ============================================ [2] Fault: [http://www.w3.org/2005/08/addressing/fault](http://www.w3.org/2005/08/addressing/fault) a:Action a:ActionMismatch The SOAP action specified on the message, '', does not match the HTTP SOAP Action, 'http://example.org/action/echoIn'. #### Environment Operating System: All Platform: All #### Affected Versions [current]
glassfishrobot commented 17 years ago

Reported by karthikeyan_k@java.net

glassfishrobot commented 17 years ago

karthikeyan_k@java.net said: Correction: The faultstring in the response is

The SOAP action specified on the message, '', does not match the HTTP SOAP Action, ''.
glassfishrobot commented 17 years ago

vivekp@java.net said: So what is the bug here? Can you not update your client application to check for ActionMismatch?

Please specify the bug in JAXWS that we can fix to resolve your issue. From the description below it looks like its bug with Indigo and you need to fix your test or client application.

glassfishrobot commented 17 years ago

karthikeyan_k@java.net said: As I mentioned, this looks like a Indigo side issue. This bug was filed for tracking purposes as I was not 100% sure that this was definitely an indigo issue. The client application cannot be modified to check for ActionMismatch as the W3C-1147 testcase mentions that MessageAddressingHeaderRequired should be returned. A mail has been sent to Kirill/Nathan and they are looking into it.

glassfishrobot commented 17 years ago

vivekp@java.net said: I checked the wsa interop test 1147 and I see that jaxws is doing things correctly.

I am closing this bug as invalid. For tracking purpose you may like to report an issue to different category, maybe we need an indigo category in wsit.

glassfishrobot commented 17 years ago

mmatula@java.net said: This issue was fixed before we created 1.0 branch, so the fix is in 1.0 -> setting target milestone to say so.

glassfishrobot commented 17 years ago

Was assigned to vivekp@java.net

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA WSIT-287

glassfishrobot commented 17 years ago

Marked as incomplete on Tuesday, November 13th 2007, 11:46:28 pm