[TUSCANY-1292] Defining a service within a component definition as an alternative to promoting as a composite service results in a wrong behaviour

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Java-SCA-0.90
• Fix Version/s: Java-SCA-1.0
• Component/s: SCA Java Runtime
• Assignee: Unassigned
• Reporter: S Venkatakrishnan
• Created: 17/May/07 13:03
• Updated: 18/Sep/10 11:29
• Resolved: 17/Aug/07 22:31

Description

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.