Issue 62 in peaberry: NPE stopping bundle that had issues starting

[peab...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 62 by ydewit: NPE stopping bundle that had issues starting
http://code.google.com/p/peaberry/issues/detail?id=62

Here is the exception I got when trying to stop a bundle after it got in
Issue 60:

java.lang.NullPointerException
at
org.ops4j.peaberry.activation.internal.ExportBundleRoot.deactivate(ExportBundleRoot.java:35)
at
org.ops4j.peaberry.activation.internal.ExportBundleRoot.deactivate(ExportBundleRoot.java:22)
at
org.ops4j.peaberry.activation.internal.InstanceBundleRoot.deactivate(InstanceBundleRoot.java:51)
at
org.ops4j.peaberry.activation.internal.BundleActivation.deactivate(BundleActivation.java:194)
at
org.ops4j.peaberry.activation.internal.BundleActivation.update(BundleActivation.java:153)
at
org.ops4j.peaberry.activation.internal.StateBundleActivationTracker.stop(StateBundleActivationTracker.java:45)
at
org.ops4j.peaberry.activation.internal.BundleActivation.stop(BundleActivation.java:142)
at
org.ops4j.peaberry.activation.internal.BundleTracker.stop(BundleTracker.java:112)
at
org.ops4j.peaberry.activation.internal.BundleTracker.bundleChanged(BundleTracker.java:86)
at
org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:807)
[Gogo shell] DEBUG com.frevvo.pellet.data.gae - ServiceEvent UNREGISTERING

Maybe it got into a bad state after the first exception (Issue 60), but in
any case, it should be a no brainer to avoid this NPE.

[peab...@googlecode.com]

Updates:
Status: Fixed

Comment #1 on issue 62 by Rinsvind: NPE stopping bundle that had issues
starting
http://code.google.com/p/peaberry/issues/detail?id=62

Fixed the issue. Now when the startup of the initial singletons fails we
stop all singletons that were started before the failure occurred.