I've finished the final piece to bringing up the base standalone
runtime which Jeremy has been working on to support the SCA 1.0
client APIs. This mostly involved externalizing autowire from
CompositeComponent to an AutowireResolver which is called after the
model is loaded. This had the side-effect of simplifying the runtime
as the connector no longer needs to deal with the autowire case
(autowires will resolve to absolute URIs).
I have also removed the process for connecting artifacts from
CompositeComponent to Deployer.
Below are a few more changes I plan to work on over the next few days:
- I plan to continue refactoring Component to simplify and cleanup
the interface. This will hopefully result in little difference
between atomic and composite components.
- I would like to eliminate the need for outbound and inbound wires,
having the connector create a single Wire which is attached to a
source. In this scenario, targets will not have wires but will
continue to supply TargetInvokers to sources. This will tie in
directly with Meeraj's work on the physical component builders and
wire reconstitution on slaves. It will also further serve to simplify
the connect phase. As we do this, we will need to revisit the SPI for
WirePostProcessors. Following on Meeraj's physical builder work,
policy and wire processing will need to be done on the master against
the model and a portable representation of the wire sent to slaves
where it will be constituted. We will need something akin to an
InterceptorBuilder which will be responsible for helping to
constitute a wire on the slave by supplying interceptors. Thoughts?
- Integrate the autowire changes with Meeraj's federation work which
will give us support for federated/distributed autowire across an SCA
Domain (as well as supporting more of the SCA autowire semantics).
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
