Community
Participate
Working Groups
The BundleException class has been enhanced to allow for error code types to be specified. The following error codes have been defined (see the latest javadoc for explaination): UNSPECIFIED UNSUPPORTED_OPERATION INVALID_OPERATION MANIFEST_ERROR RESOLVE_ERROR ACTIVATOR_ERROR SECURITY_ERROR STATECHANGE_ERROR NATIVECODE_ERROR DUPLICATE_BUNDLE_ERROR The Framework needs to be updated to use the appropriate type when creating BundleExceptions.
Created attachment 110850 [details] patch + testcases I scanned the equinox code and added BundleException types where I thought it was appropriate. I also added a few testcases. The tests are not complete by any means but at least do a fair job at sniff testing the changes.
Patch released to HEAD.
Hi Tom, quick question: it seems the osgi.jar inside supplemental was not updated accordingly. If the supplemental project were going to be compiled against the bundled osgi.jar (not sure it was the intention), it will fail because the source code refers to a constant in BundleException that does not exist in the osgi.jar.
(In reply to comment #3) > Hi Tom, quick question: it seems the osgi.jar inside supplemental was not > updated accordingly. If the supplemental project were going to be compiled > against the bundled osgi.jar (not sure it was the intention), it will fail > because the source code refers to a constant in BundleException that does not > exist in the osgi.jar. > which osgi.jar? The one from the OSGi R4 V4.1 specification? The supplemental project must be compiled against the upcoming osgi.jar from the OSGi R4 V4.2 specification. It will no longer be able to compile against the V4.1 osgi.jar.
(In reply to comment #4) > (In reply to comment #3) > > Hi Tom, quick question: it seems the osgi.jar inside supplemental was not > > updated accordingly. If the supplemental project were going to be compiled > > against the bundled osgi.jar (not sure it was the intention), it will fail > > because the source code refers to a constant in BundleException that does not > > exist in the osgi.jar. > > > > which osgi.jar? The one from the OSGi R4 V4.1 specification? The supplemental > project must be compiled against the upcoming osgi.jar from the OSGi R4 V4.2 > specification. It will no longer be able to compile against the V4.1 osgi.jar. > Sorry, you explicitly told me the one under the supplemental project. :) This jar does not belong here. It is not used in the compilation of the supplement project. I will need to remove that jar.
