Lou Amodeo wrote:
This is a request to propogate the value of a references target= attribute
as a first class attribute on its associated bindings model object.
This request is based on a requirement to provide support to implement a
late-endpoint resolution capability for service references when a reference
specifies the target= attribute. This value in conjunction with a domain
wide services registry allows the binding invokers to use the value
specified for <reference target="" as a key to perform a service lookup to
obtain the services endpoint URI dynamically during the invocation of the
service rather than during compositie startup. The primary benefits of this
approach are to provide a degree of location transparency for services and
remove the requirement of the client from knowing the services endpoint at
installation time. This would only apply to clients that are running in the
same domain as the services they reference.
After reading the whole thread I'm confused and would like to walk
through a simple scenario with two composites A and B, A containing
component references to components in B.
Here are the steps I'm thinking about for A and B:
A1. contribution A is installed in the domain.
A2. deployable composite A is selected for deployment.
A3. policy sets are configured and applied to elements of A.
A4. A's references and dependencies are validated and satisfied.
A5. composite A is deployed to SCA machine 1.
A6. components in composite A are started.
A7. a reference wired to a component in B is invoked.
B1. contribution B is installed in the domain.
B2. deployable composite B is selected for deployment.
B3. policy sets are configured and applied to elements of A.
B4. B's references and dependencies are validated and satisfied.
B5. composite B is deployed to SCA machine 2.
B6. components in composite B are started.
B7. a reference wired to a component in B is invoked.
By SCA machine I mean a logical processor responsible for instantiating
components and executing their implementations (a server, a process, a
node, a webapp, or whatever applies to your particular architecture).
Would it be possible to describe the timing of the A steps function of
the B steps, for example
A1 < B1
A2 < B1
A3 < B1
A4 > B5?
etc?
That will help me understand your requirement and what you're expecting
of the various configuration and resolution steps.
Thanks!
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
