Domain Manager GUI does not put <binding.sca> entries in generated node confiig
files
-------------------------------------------------------------------------------------
Key: TUSCANY-3193
URL: https://issues.apache.org/jira/browse/TUSCANY-3193
Project: Tuscany
Issue Type: Bug
Components: Java SCA Domain Management
Affects Versions: Java-SCA-1.5.1
Reporter: Simon Nash
Assignee: Simon Nash
Fix For: Java-SCA-1.5.1
When creating a domain configuration from scratch using the Domain Manager GUI,
the generated configuration files for nodes in the "cloud" directory don't have
a <binding.sca> entry. These files currently have host/port entries for
binding.ws, binding.http, binding.jsonrpc, and binding.atom, but no host/port
entry for binding.sca.
Without this entry, application composites sent to the nodes by the domain
manager will always have local-only <binding.sca> entries, which means they
can't use binding.sca to communicate between different nodes. This applies to
both forward calls and callbacks.
In order to get binding.sca to work across distributed nodes, it's currently
necessary to manually edit the generated files in the "cloud" directory and add
<binding.sca> elements to the node definitions. This is a serious usability
issue for someone who wants to use the distributed domain in the simplest
possible manner.
A complete fix for this problem requires the following:
1. Add <binding.sca> elements to the generated configuration.
2. Change the builder code so that the presence of these elements does not
force all binding.sca calls to use a distributed provider, which would create
unnecessary overhead when the reference and the target are running on the same
node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
