[
https://issues.apache.org/jira/browse/TUSCANY-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867141#action_12867141
]
ant elder commented on TUSCANY-3554:
------------------------------------
I've just made a couple of fixes and better exception messages to the client
api so could you try now with the latest code and if its still not working
paste in here the client api calls that you are using?
> Two Issues found when using SCAClientFactory
> ---------------------------------------------
>
> Key: TUSCANY-3554
> URL: https://issues.apache.org/jira/browse/TUSCANY-3554
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Assembly Model
> Reporter: Yang Lei
>
> I tried to use SCAClientFactory to access the SCA services defined by sample
> "sample-implementation-java-calculator". And found two issues.
> There is the code:
> SCAClientFactory factory = SCAClientFactory.newInstance(new
> URI("default"));
> CalculatorService service =
> factory.getService(CalculatorService.class, "CalculatorServiceComponent");
> System.out.println("1+1="+service.add(1, 1));
> Issue 1. The domain uri passed in the SCAClientFactory does not seem to
> affect the result.
>
> As I can change "default" to any string w/o changing the
> contribution start code, I will get the same result.
>
> Issue 2. Different call path using componentName v.s.
> componentName/serviceName to get the service.
> When I use componentName/serviceName instead of just the
> componentName, the invocation on the services requires hazelcast related jars
> in the classpath , with other settings like port .
> Note: The bootstrapping of the sample-implementation-java-calculator is using
> the similar code as TuscanyRuntimeBridge which start a Node with the
> contribution jar and the composite uri.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
