[
https://issues.apache.org/jira/browse/TUSCANY-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510319
]
耿韶光 commented on TUSCANY-1411:
------------------------------
Things goes like this, There is a runaround of this issue, and now it seems not
a bug!
Original error comes from the two interfaces implementation, the sca runtime
just got to know one of them, I change the secquence of the two interfaces in
the code, then the wrong service call worked, and the right one not.
Now I change the client code into getService([component class],[component
name]/[interface name without the package perfix]), OK now it works.
But it seems not a nice way, for the situation, getService call like this will
puzzle the developer.
> JDKInvocationHandler works wrong when a component references more than one WS
> -----------------------------------------------------------------------------
>
> Key: TUSCANY-1411
> URL: https://issues.apache.org/jira/browse/TUSCANY-1411
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-Next
> Environment: windows xp, java5
> Reporter: 耿韶光
>
> I extended ws-service and ws-reference sample with 2 services, original it
> has only one reference of web service which was referenced by a component.
>
> Up to now, I add a second service, then things go wrong:
>
> The original component implements a service interface, with "getService"
> method, the client got the instance(a proxy) of the service interface, then
> the client could invoke the method on the service interface.
> But now the component implements the second service interface, then the
> org.apache.tuscany.sca.core.invocation.JDKInvocationHandler seems could not
> recognize the right generic of the component.
--
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]
