Page History

...

1. add/list/remove contributions/composites/nodes
2. analyze/resolve/validate contributions and their dependencies
3. include composite (from the contributions above) in a domain
   1. A matter of selecting which composites will be top level composites in the domain
4. associate composites with nodes/apply physical binding defaults/propagate physical addresses based on domain level wiring
   1. Get contributions - hoping this is all done by previous steps
   2. For each contribution included
   3. Find all artifacts in the contribution
   Read each artifact and create a model (apart from composites which are done later)
   4. Enhance model with policy information
   5. resolve models against artifacts from contribution and its dependencies (not sure I need this)
   Read in node model - which provides
   1. Mapping of composite to node
   2. Default configuration of bindings at that node, e.g. the root URL required for binding.ws
   6. For each composite in the domain (assuming I have access to the resolved composite model)
      1. Find, from the node model, the node which will host the composite
      2. for each service in the composite
         1. find each binding in the service
            1. Take the default binding configuration and apply it to the binding
            2. What to do about URLs as they may be either
               1. Unset
               2. Set absolutely
               3. Set relatively
               4. Set implicitly (from WSDL information)
5. read/compile-build/write composites without requiring a runtime

...