I'm starting to get stuck into the final pieces for having the
Connector support federated deployment. I plan to implement the
following algorithm in the FederatedDeployer to deploy a
PhysicalChangeSet:
1. For each resource definition, build resource
2. For each PhysicalComponentDefinition build the component
3. Register built components with the ComponentManager
4. For each PhysicalWireDefinition, cakk connect
- Build interceptors
- Attach the wire to target Component
- Attach the wire to source Component
5. Start the components
If we do this, we can also get rid of ServiceBinding and
ReferenceBinding from the runtime and instead just use Components to
connect wires from and to physical transports. For example, a binding
would be implemented as a Component instead of a ServiceBinding and
ReferenceBinding. This will mean the only extension type we need to
support is a Component. When the Connector attaches the Wire to the
source and target Components, it will pass the PhysicalSource/
TargetDefinition part of the PhysicalWireDefinition. This will be
extensible by binding type and will contain information necessary to
expose or consume services over a binding. The PhysicalSource/
TargetDefinition will be created on the master and marshalled as part
of the PhysicalWireDefinition.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
