Comments inline.
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>
Sent: Wednesday, September 05, 2007 9:03 AM
Subject: Re: Issue with dynamic creation of
NotificationReferenceBindingProvider
[snip]
Raymond Feng wrote:
At this moment, the code works as Ignacio described. We defer the
activation of a reference to the first time it's used for invocation. If
we decide that we need to agressively start the reference bindings, we
can add the part back to CompositeActivatorImpl.
Thanks,
Raymond
I think we need to activate references when the component that owns them
is activated, to keep the semantics of of start()/stop() clear, and allow
providers to perform any initialization they need on references (which are
not so different from services in many aspects).
There are some differences. A reference can be dynamically created and it is
possible that a reference binding won't be selected at all.
As a balance, can we do the following?
1) During the activation of a component, we add the reference binding
providers to the defined references. Then the binding provider will have a
chance to do some initialization (for example, handle subscription).
2) When the reference is used for invocation, we start the binding provider
(further initilization can be performed at this time) and create the
wire/invocation chains.
Thanks,
Raymond
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
