Hi Raymond,
  After re-investigated the code, it means to me not a bug in fact, sorry for 
my "bugging shout".
  But there is something should be noticed: for sample ws-ref/ws-service, the 
client component class implemented a interface or two, This demostration is not 
right!
   
  Client generic is proxy casted, the component class is proxied to the service 
interface, so it does not need(or should not) implement the service interface 
by itself, it is a pretty feature that the client and server side is looser 
coupled.
   
  So from the sample(ws-ref/ws-serv)'s point of view, the service consumer's 
programming model should be documented.

"Raymond Feng (JIRA)" <tuscany-dev@ws.apache.org> wrote:
  
[ 
https://issues.apache.org/jira/browse/TUSCANY-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng resolved TUSCANY-1411.
-----------------------------------

Resolution: Invalid
Fix Version/s: Java-SCA-Next

My understanding is that you said it's NOT a bug. Please speak out if I get it 
wrong.

> 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: 耿韶光
> Fix For: Java-SCA-Next
>
>
> 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]



 
---------------------------------
TV dinner still cooling?
Check out "Tonight's Picks" on Yahoo! TV.

Reply via email to