[Peter Kriens] Of course you're right that there is an issue with when
you consider
the application to have started, whether successfully or
unsuccessfully. DS does not consider a component with unsatisfied
references to be any kind of error, because the services that would
make it a satisfied
On Thu, Feb 17, 2011 at 5:02 PM, Eugen Reiswich
ereisw...@googlemail.com wrote:
make it a satisfied component may be coming along very soon... so,
when should an error be thrown?
That's exactly the question I was not able to answer!
As Chris points out... this is not something that DS can
On 19 Feb 2011, at 11:25 , Neil Bartlett wrote:
You could simply write a bundle that starts all bundles and waits for
them to reach ACTIVE state (a BundleListener or BundleTracker will
help you with this part). Once all the bundles you know about are
active, your system should be in its
