[
https://issues.apache.org/jira/browse/TUSCANY-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596503#action_12596503
]
Scott Kurz commented on TUSCANY-2316:
-------------------------------------
The binding-ws-axis2 is overwriting the databinding on the IC obtained from the
binding.ws model object (WebServiceBindingImpl). So far, that would seem to
be correct, then.
What do the ClassCastExceptions you're getting look like?
> Axis2 Binding Provider does not handle services & references with WSDL
> interfaces correctly
> -------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2316
> URL: https://issues.apache.org/jira/browse/TUSCANY-2316
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-1.2
> Environment: - any -
> Reporter: Mike Edwards
> Assignee: Mike Edwards
> Fix For: Java-SCA-Next
>
> Attachments: sample-helloworld-bpel-ws.zip
>
>
> Where a component has a service or reference which has an interface which
> uses a WSDL interface definition, the Axis2 binding providers incorrectly
> overwrite the DataBinding specified by the component implementation and
> impose the OMElement binding used by Axis2 - this causes class cast
> exceptions when the service or reference is invoked.
> The problem is caused by failure to copy the InterfaceContract definition in
> the Axis2ReferenceBindingProvider and Axis2ServiceBindingProvider
> constructors, when the InterfaceContract is not a JavaInterfaceContract. The
> lack of a copy means that the Axis binding provider then uses the original
> contract object as its own and overwrites aspects of that contract -
> including the databinding to use.
> I've attached a sample application that I created which found this problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
