You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Vamsavardhana Reddy (JIRA)" <de...@tuscany.apache.org> on 2008/08/22 19:34:44 UTC

[jira] Resolved: (TUSCANY-2562) Callback issue when reference is set with getter & setter method

     [ https://issues.apache.org/jira/browse/TUSCANY-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vamsavardhana Reddy resolved TUSCANY-2562.
------------------------------------------

    Resolution: Fixed

Completed: At revision: 688128  in trunk.

> Callback issue when reference is set with getter & setter method
> ----------------------------------------------------------------
>
>                 Key: TUSCANY-2562
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2562
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Java Implementation Extension
>    Affects Versions: Java-SCA-Next
>         Environment: Windows XP SP2, IBM JDK 1.5
>            Reporter: Ramkumar Ramalingam
>            Assignee: Vamsavardhana Reddy
>             Fix For: Java-SCA-Next
>
>
> I see this strange issue, while working with callbacks using sample callback-ws-client. To re-produce this exception, first start the CallbackServer.java from callback-ws-service sample and
> Just replaced the reference set with annotations as shown below in MyClientImpl.java at line number 37 in callback-ws-client sample....
>   
>    @Reference
>    protected MyService myService;
> with the getter and setter method as shown below.
>    
>    //@Reference
>    //protected MyService myService;
>    
>     protected MyService myService;
>     public void setMyService(MyService theBean) {
>         this.myService = theBean;
>     }
>     public MyService getMyService() {
>         return this.myService;
>     }
> I was under an impression that, both means the same and should not have any issue. But things are different in this case.
> Now the sample, seems to throw an exception as shown below.
> aClientMethod return from someMethod on thread Thread[main,5,main]
> Aug 22, 2008 4:32:56 PM org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver invokeBusinessLogic
> SEVERE: No matching operation for receiveResult is found in service MyClientComponent#myService
> org.osoa.sca.ServiceRuntimeException: No matching operation for receiveResult is found in service MyClientComponent#myService
> 	at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:178)
> 	at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:109)
> 	at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChain(RuntimeWireImpl.java:115)
> 	at org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:84)
> 	at org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:79)
> 	at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.invoke(RuntimeWireImpl.java:138)
> 	at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(Axis2ServiceProvider.java:687)
> 	at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:68)
> 	at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)
> 	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
> 	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
> 	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
> 	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
> 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
> 	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:354)
> 	at org.apache.tuscany.sca.core.work.Jsr237Work.run(Jsr237Work.java:63)
> 	at org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$DecoratingWork.run(ThreadPoolWorkManager.java:221)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> 	at java.lang.Thread.run(Thread.java:803)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.