...
- add/list/remove contributions/composites/nodes
- analyze/resolve/validate contributions and their dependencies
- include composite (from the contributions above) in a domain
- A matter of selecting which composites will be top level composites in the domain
- associate composites with nodes/apply physical binding defaults/propagate physical addresses based on domain level wiring
- Read in node model - which provides
- Mapping of composite to node
- Default configuration of bindings at that node, e.g. the root URL required for binding.ws
- For each composite in the domain (assuming I have access to the resolved composite model)
- Find, from the node model, the node which will host the composite
- for each service in the composite
- If there are no bindings for the service
- Create a default binding configured with the default URI from the node model
- else
- find each binding in the service
- Take the default binding configuration and apply it to the binding
- What to do about URLs as they may be either
- Unset
- Apply algorithm from Assembly Spec 1.7.2
- Set
- relatively
- Apply algorithm from Assembly Spec 1.7.2
- Set absolutely
- Assume it is st correctly
- Set implicitly (from WSDL information)
- Assume it is set correctly
- Unset
- find each binding in the service
- If there are no bindings for the service
- Read in node model - which provides
- read/compile-build/write composites without requiring a runtime
...