[
https://issues.apache.org/jira/browse/TUSCANY-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509538
]
Simon Laws commented on TUSCANY-1379:
-------------------------------------
As part of the distributed runtime there is an implementation of a node
(somewhere where Tuscany applications can run) that contains a NodeSCADomain
instance which is provided to run a composite containing management components.
The node looks for a file called nodename.node which is actually just a normal
composite file. I have only created one management component to date,
ComponentRegistry, but of course it's easy to create new ones and use all of
the facilities to expose them to the outside world.
The node can also contain 1 or more DistributedSCADomains. These are pretty
similar to the embedded domain with a few small exceptions. Once change is that
the DistributedSCADomain holds a reference to the NodeSCADomain and in this way
various parts of the runtime can get hold of local references to management
components as required.
One thing that worries me about this is that the .node file is expected to hold
a specific set of management components for the node to work and I haven't
included specific validation to ensure that this is the case yet.
> Admin:Core start/stop/query admin services
> ------------------------------------------
>
> Key: TUSCANY-1379
> URL: https://issues.apache.org/jira/browse/TUSCANY-1379
> Project: Tuscany
> Issue Type: Improvement
> Affects Versions: Java-SCA-Next
> Reporter: ant elder
> Fix For: Java-SCA-Next
>
>
> Admin:Core start/stop/query admin services - implement basic core services to
> start/stop/query running components.
--
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]
