] wrote:
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
Ignacio Silva-Lepe wrote:
The thread has gone quiet and I am not sure we have
reached a conclusion.
In summary, binding-notification relies on both the
activation and start phases to occur early for the
reference binding provider, that is, at the same time
as for the service binding provider.
Subject: Re: Issue with dynamic creation of
NotificationReferenceBindingProvider
Ignacio Silva-Lepe wrote:
The thread has gone quiet and I am not sure we have
reached a conclusion.
In summary, binding-notification relies on both the
activation and start phases to occur early for the
reference
Comments inline.
[snip]
Raymond Feng wrote:
What do you mean by a reference can be dynamically created? can you
please describe the scenario you have in mind?
There are a few cases:
1) SCADomain.getService() will create self reference
2) ComponentContext.createSelfReference()
3)
Comments inline.
On 9/5/07, Raymond Feng [EMAIL PROTECTED] wrote:
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
Comments inline.
On 9/4/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Ignacio Silva-Lepe wrote:
Part of the design of binding-notification is that
NotificationReferenceBindingProvider
serves as a producer service to handle subscription requests from
consumers.
Because of this,
Message -
From: Ignacio Silva-Lepe [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, September 05, 2007 5:52 AM
Subject: Re: Issue with dynamic creation of
NotificationReferenceBindingProvider
Comments inline.
On 9/4/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote
[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.
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
Raymond Feng wrote:
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
Hi,
Comments inline.
Thanks,
Raymond
- Original Message -
From: Jean-Sebastien Delfino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, September 05, 2007 1:31 PM
Subject: Re: Issue with dynamic creation of
NotificationReferenceBindingProvider
Raymond Feng wrote
So, more specifically, I'd like to propose the following
changes:
1- Add a boolean supportsDynamicReferenceActivation
method to o.a.t.s.provider.BindingProviderFactory
2- Change o.a.t.s.core.Assembly.CompositeActivator-
Impl.activate(Composite) to once again call activate
for a component's
Ignacio Silva-Lepe wrote:
Part of the design of binding-notification is that
NotificationReferenceBindingProvider
serves as a producer service to handle subscription requests from consumers.
Because of this, the code was relying on
NotificationReferenceBindingProvider
being created early, at
Part of the design of binding-notification is that
NotificationReferenceBindingProvider
serves as a producer service to handle subscription requests from consumers.
Because of this, the code was relying on
NotificationReferenceBindingProvider
being created early, at activation time of components
14 matches
Mail list logo
