[
https://issues.apache.org/jira/browse/AXIS2-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Katherine Sanders updated AXIS2-4596:
-------------------------------------
Attachment: 632660.patch
Here's a patch that fixes the problem. I've modified BindingProvider to check
if addressing is turned on in the WSDL when it's setting the default. I've
also added some unit tests to check that UsingAddressing is correctly read from
the WSDL, that addressing is off by default if there isn't a WSDL or the WSDL
doesn't contain UsingAddressing, and that addressing is on if the WSDL contains
UsingAddressing.
> Client unable to turn on addressing with UsingAddressing in the WSDL
> --------------------------------------------------------------------
>
> Key: AXIS2-4596
> URL: https://issues.apache.org/jira/browse/AXIS2-4596
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Reporter: Katherine Sanders
> Attachments: 632660.patch
>
>
> Revision 702224 defaulted DISABLE_ADDRESSING_FOR_OUT_MESSAGES to true in
> BindingProvider, however it didn't add any code to turn addressing on if
> <wsaw:usingAddressing /> is present in the WSDL. This means that addressing
> is always off on the client unless AddressingFeature is used to turn it on,
> and that's only available in JAX-WS 2.1 clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
