Add Timeout, BundleException, and logging for activation failure

[mcculls]

Originally reported on Google Code with ID 68

If a bundle module is activated via the Peaberry activation framework, but references
a configurable that is not available via config-admin, then the bundle fails to activate.

However, the bundle state switches to STARTED, and there is no indication to the user
that the activation failed, and no reason for the failure given.

As per the discussion here:

https://groups.google.com/d/topic/guice-osgi/kNStOJ0ZGxg/discussion

it would be great to have the bundle activation:

1) Timeout if dependencies / configuration values are not available during activation.

2) Log the dependency / configuration that is not available, probably at WARN level.

3) Throw a BundleException with the failure information.

Reported by rocketraman on 2011-10-24 16:31:53

[mcculls]

Another idea would be to add default values for every configurable. And log something
like "Configuration X not available: using default Y for setting Z". When the configuration
comes along the new values will be injected in place of the defaults.

Reported by Rinsvind on 2011-10-24 18:39:01

[mcculls]

Issue 67 has been merged into this issue.

Reported by mcculls on 2011-10-28 01:04:34

[mcculls]

Reported by mcculls on 2012-08-04 21:36:24

• Labels added: Peaberry-Extension