Hi,
The "start" of a node consists of two steps:
1. Bootstrap the Tuscany runtime and extensions: It discovers the extension
points and extensions and populate them.
2. Load contributions and deployable composites. Resolve/Build the
composite. And then activate the components (implementation, service and
reference).
I envision there is a configuration for the node. The configuration will
contain the following information:
a) A list of contributions
b) One or more composites (which can be included into a deployment
composite)
c) Base URIs for various bindings, such as "http://locahost:9080/"; for
binding.ws
d) Other settings for the specific host platform
Does your "restart" mean the steps below?
1) Deactivate the composites and clean up the models
2) Change the node configuration (Do you require in-memory change of the
models?)
3) Activate the composites again
Thanks,
Raymond
--------------------------------------------------
From: "Giorgio Zoppi" <[email protected]>
Sent: Monday, February 02, 2009 1:06 PM
To: <[email protected]>
Subject: Tuscany Composite and domain.
Hi to all,
I'm back finally and seeing your composite and node api. I wonder if
it's feasible to replace a composite in node, i.e. the following
steps:
+ stop a node composite
+ get the composite model, and change it
+ start a node with the new composite, different from the previous.
This is the first part. Any hints about?
(I did something a while ago, but it required to modify the assembly
package, thing that i don't want this time)
--
Quiero ser el rayo de sol que cada día te despierta
para hacerte respirar y vivir en me.
"Favola -Moda".
