[
https://issues.apache.org/jira/browse/AXIS2-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Katherine Sanders updated AXIS2-4922:
-------------------------------------
Attachment: AXIS2-4922.patch
The attached patch fixes the problems by making the following changes:
1. WSDL11ActionHelper should be updated to check for "" as well as null in
getActionFromInputElement, getActionFromOutputElement and
getActionFromFaultElement so that the default action pattern is used instead.
2. The code in JavaDispatcher.setFaultResponseAction gets the fault action from
the fault class name, which works for java2wsdl services but in the wsdl2java
case there isn't any code that maps from the WSDL fault name to the java class
name. I've modified the code in WSDL11ToAxisServiceBuilder to add entries to
the fault action map for the possible class names using the mapping rules in
the JAX-WS 2.2 specification. I've also changed the JavaDispatcher code to
look for the new mappings if it doesn't find the action using the existing code.
> JAX-WS 2.2 CTS failures in WS-A metadata action code
> ----------------------------------------------------
>
> Key: AXIS2-4922
> URL: https://issues.apache.org/jira/browse/AXIS2-4922
> Project: Axis2
> Issue Type: Bug
> Components: Addressing
> Reporter: Katherine Sanders
> Attachments: AXIS2-4922.patch
>
>
> A number of JAX-WS 2.2 CTS failures occur due to the following issues with
> the WS-A metadata action code:
> 1. If a WSDL is used with wsam Action = "" on the input for the operation,
> the client request will fail to send because there's no action to add to the
> header
> 2. If a WSDL is used with more than one fault on an operation, the wsam
> Action from the first fault will always be used even if one of the other
> faults is thrown.
--
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]
