On Fri, Aug 22, 2008 at 12:16 PM, Ramkumar R <[EMAIL PROTECTED]> wrote:
> Hi All,
> I see this strange issue, while working with callbacks using sample
> callback-ws-client. Here is what i tried....
>
> I just replaced the reference set with annotations as shown below in
> MyClientImpl.java at line number 37
>
> @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)
>
> Is it mandatory that, only annotations should be used in case of Callbacks?
>
> --
> Thanks & Regards,
> Ramkumar Ramalingam
>
Hi Ram
Can you try annotating the setter method with @Reference and see what
happens.
Simon
