Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  1. Static domain - where all composites are present before nodes are started
    • as now composites will automatically be configured with unwired bindings
  2. Incremental deployment - where nodes are started with composites before the domain is complete
    • Endpoint logic will ask the domain for information required to resolve endpoint references with endpoints
  3. Service Location Transparency - a future scenario where nodes can be moved
    • Endpoint/binding logic can again be used to ask the domain for new endpoint information
    • Could just let each binding handle it but maybe some advantage to having the enpoint reference handle it by stopping/reconfiguring/starting the binding
  4. Dynamic Domain - in the future but some scenarios call for components to be reconfigured at runtime
    • Endpoint reference and endpoint concepts focus the effort of adding removing wires

Overview

Model

Callback

Promotion

...

Action

Description

Read Model

read composite file into in-memory model

Resolve Model

resolve composite against other artifacts in the composite and domain

Build model

create the appropriate relationships between parts of the model bases on SCA validation rules, Inludes:

  • Endpoint creation
  • EndpointReference creation

Activate Runtime

Create the runtime infrastructure. Includes:

  • EndpointReference resolution
  • EndpointReference wire creation
  • Endpoint wire creation

Start Runtime

Start all runtime providers

EndpointReference resolution

Locate the services that endpoint references refer to

Build Reference Chains

use the wire configuration to build the runtime interceptor chains

...