Hi,
Am Donnerstag, den 17.02.2011, 11:59 + schrieb Neil Bartlett:
Depending on the DS implementation you may be able to introspect the
state of the components, including the ones that are unsatisfied, and
report this as a kind of startup progress. Felix DS has a handy
introspection API
[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
Hi folks,
The start up of an application is exactly where I get in trouble with OSGi.
Although using DS, my application sometimes starts with say only 8 of 10
available services due to misconfiguration. In this case I would rather throw a
RuntimeException, NPE ore something comparable to
A simple way would be to create a service with dependencies on all
your 10 services. When this service will be registered, you'll know
your application is ready.
But I agree this is a real problem and there is a need for something here.
On Thu, Feb 17, 2011 at 09:50, Eugen Reiswich
Can you clarify a bit more accurately what is going wrong? Do some of
the components not start at all, or are some not being bound into your
application component?
If the former then make sure you enable the OSGi LogService. DS will
send errors to the log service if any service fails to start,
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 component may
Hi Eugen,
This is a very interesting question, thanks for asking it!
I appreciate that dynamics are not a big feature of enterprise
applications, but there is one time when ALL applications are dynamic,
and that is during startup (also, less importantly, during shutdown).
This is what I find
