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
<[email protected]> 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
