2009/2/2 Raymond Feng <[email protected]>: > 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. yes. Yes > 2. Load contributions and deployable composites. Resolve/Build the > composite. And then activate the components (implementation, service and > reference). yes..done by various builders, and composite configurators.
> 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 Yes. This is the way, I see these stuffs. > 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?) Yes. I require to be able to reconfigure node composite at run-time. Suppose that you had to optimize the way on which the components behaves at run-time for providing a better QoS on your non functional requirements(i.e change a policy at runtime, duplicate a component a run-time, ecc). You might follow on of the two ways in the current runtime: 1) modify the composite builder, composite activator and contribution builder, node impl in order to provide a way to modify at run-time a composite which is part of a contribution. This is the way that i followed one year ago, but i think that's costly. In this way you might add a new composite item (wire, component, policy) at runtime without no risk, and with risks if you want to remove (i.e. a pending call to a component) it. 2) the steps that you indicate (1,2,3) for my point of view means: 1) stop / temp. deactivate the node composite (in order to avoid incoming calls) 2) replace in memory a composite with a newly generated composite, in which you had changed items, based on the stopped composite. 3) starting again the composite. In this way i might able to proof you (i.e.providing a demo ) that it's feasible to build a demo with SCA and some sort of autonomic features. Best Regards, Giorgio -- Quiero ser el rayo de sol que cada día te despierta para hacerte respirar y vivir en me. "Favola -Moda".
