Defining a service within a component definition as an alternative to promoting
as a composite service results in a wrong behaviour
-----------------------------------------------------------------------------------------------------------------------------------
Key: TUSCANY-1292
URL: https://issues.apache.org/jira/browse/TUSCANY-1292
Project: Tuscany
Issue Type: Bug
Reporter: Venkatakrishnan
The JSON-RPC sample
(https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/helloworld-jsonrpc/)
had the following composite :
composite xmlns="http://www.osoa.org/xmlns/sca/1.0";
targetNamespace="http://sample";
xmlns:sample="http://sample";
name="helloworldjsonrpc">
<component name="HelloWorldJSONServiceComponent">
<service name="HelloWorldService" >
<interface.java interface="helloworldjsonrpc.HelloWorldService"/>
<binding.jsonrpc/>
</service>
<implementation.java class="helloworldjsonrpc.HelloWorldServiceImpl"/>
</component>
</composite>
With this composite, when the Helloworld service is invoked this ends up
calling the JSONRPCBindingInvoker.invoke method instead of the component
implementation. When I moved the service out to the composite level (as
composite service) the behaviour is correct and the component implementation
gets invoked.
--
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]
