There was early on, but I admit I forgot the good reason it is an error vs. a no-op. Regardless, it will be difficult to change now because others may be depending on the current behavior.
I suggest you avoid checking headers though: boolean isFragment = (b.adapt(BundleRevision.class).getTypes() & BundleRevision.TYPE_FRAGMENT) != 0; Tom From: Benson Margulies <bimargul...@gmail.com> To: OSGi Developer Mail List <osgi-dev@mail.osgi.org> Date: 11/10/2016 09:59 AM Subject: [osgi-dev] Why is 'start' an error for fragments? Sent by: osgi-dev-boun...@mail.osgi.org Has there ever been consideration of making 'start' be a harmless no-op for fragment bundles? I keep having to write code to check the headers and avoid the call to start on fragments. _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
