On Feb 20, 2007, at 11:26 AM, Ignacio Silva-Lepe wrote:

Hi Jim,

I am not sure I understand one thing, maybe I am missing something.
Previously, the wire service was invoked in the build phase, as far as
I recall. This meant that by the time the connector needed to ask for
a target invoker to get created, any arbitrary component, reference or
service would have its wires available.
In particular, for (the now called) LocalReferenceBinding, when
createTargetInvoker was called on it, it could safely new up a LocalTar-
getInvoker passing it its (outbound) wire. Now that the connector is
also creating wires in the same phase, it's not clear that a LocalRe-
ferenceBinding will always have its wire by the time createTarget-
Invoker is called on it.
Does this sound right, or is there some (perhaps not so) subtle thing
I am missing?

Yeah. I thought about solving this by just having the TargetInvoker point back to the Service/ReferenceBinding to get the wire lazily which should be a simple change but then it dawned on me we don't need local composite services or references at all and should be able to just get rid of them. Similar to how the AutowireResolver works, we need to introduce a "normalization" phase that is run over the model where intermediate hops are factored out of a wire. Harking back to a previous post, it should be the case that /all/ wires in an SCA domain are normalized to one of the following:

1. Atomic Component Reference ---->Atomic Component Service
2. Atomic Component Reference ---->to a physical transport (via a ReferenceBinding) 3. physical transport (via a ServiceBinding)---->Atomic Component Service 4. physical transport (via a ServiceBinding)---->to a physical transport (via a ReferenceBinding)

All local bindings would be nornalized to case 1 and hence exist only as component-component interactions. This means that the local reference and service bindings should be able to just go away.

Meeraj was working on the slave side of the wire building. We were going to start on the master part where this normalization would happen (probably) tomorrow.

Does this address the issue you were raising?

Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to