You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by David Blevins <da...@visi.com> on 2009/04/29 22:10:35 UTC
[blueprint] Initialization
How much or how little of the triggered initialization guarantees are
implemented so far? Did some very similar synchronization guarantees
for EJB 3.1 singleton lazy initialization.
-David
Re: [blueprint] Initialization
Posted by Guillaume Nodet <gn...@gmail.com>.
The lazy bundle activation policy has not been implemented yet.
On Thu, Apr 30, 2009 at 19:53, David Blevins <da...@visi.com> wrote:
> Referring to this section on Initialization.
>
> If the instantiation phase is caused by one of the trigger services then it
> must run synchronously with the getService method invocation that triggered
> the continuance. This allows the service request to return a service
> object from the initialized Blueprint Context. All other and subsequent
> service
> requests on trigger services must block until the instantiation process
> has completely finished.
>
> Otherwise, the instantiation process must run asynchronously from the
> Bundle STARTED event. Race conditions between this event and the trigger
> services must be properly managed without causing errors.
>
>
>
> -David
>
>
> On Apr 29, 2009, at 9:36 PM, Guillaume Nodet wrote:
>
>> Not sure what you're talking about...
>>
>> On Wed, Apr 29, 2009 at 22:10, David Blevins <da...@visi.com>
>> wrote:
>>>
>>> How much or how little of the triggered initialization guarantees are
>>> implemented so far? Did some very similar synchronization guarantees for
>>> EJB 3.1 singleton lazy initialization.
>>>
>>> -David
>>>
>>>
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: [blueprint] Initialization
Posted by David Blevins <da...@visi.com>.
Referring to this section on Initialization.
If the instantiation phase is caused by one of the trigger services
then it
must run synchronously with the getService method invocation that
triggered
the continuance. This allows the service request to return a service
object from the initialized Blueprint Context. All other and
subsequent service
requests on trigger services must block until the instantiation
process
has completely finished.
Otherwise, the instantiation process must run asynchronously from the
Bundle STARTED event. Race conditions between this event and the
trigger
services must be properly managed without causing errors.
-David
On Apr 29, 2009, at 9:36 PM, Guillaume Nodet wrote:
> Not sure what you're talking about...
>
> On Wed, Apr 29, 2009 at 22:10, David Blevins
> <da...@visi.com> wrote:
>> How much or how little of the triggered initialization guarantees are
>> implemented so far? Did some very similar synchronization
>> guarantees for
>> EJB 3.1 singleton lazy initialization.
>>
>> -David
>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: [blueprint] Initialization
Posted by Guillaume Nodet <gn...@gmail.com>.
Not sure what you're talking about...
On Wed, Apr 29, 2009 at 22:10, David Blevins <da...@visi.com> wrote:
> How much or how little of the triggered initialization guarantees are
> implemented so far? Did some very similar synchronization guarantees for
> EJB 3.1 singleton lazy initialization.
>
> -David
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com