Community
Participate
Working Groups
start Equinox with config.ini and framework start level is set to 1 get all the installed bundles and update the one that has native code and bundle state has to be either installed or resolved raise the framework start level to its proper value to start all the bundles The test bundle which is accessing the updated bundle via OSGi service discovery failed due to ClassCastException Without doing update then this problem is not occurring. The reason I am doing bundle update is because the bundle has native code and it is loaded via "reference" in the config.ini and I want the Equinox to reload the native code from the subsequent run. If this is not the right way for that then maybe someone can point out the proper way.
- Does the bundle you update export the package which is used to publish a service? - Do you get the ClassCastException when try to case the service object gotten from BundleContext.getService method? - Have you tried running call PackageAdmin.refreshPackages on the updated bundle? Does that help? I'm a bit confused by the scenario. Did you install a new version of the bundle with updated native code? How did you do that, using OSGi API or by file replacement? Are you restarting the VM or attempting to restart the framework without a VM restart and then running into issues loading the native library from the same path? If that is the case this sounds like bug 156873 which got fixed in 3.2.2.
This may be released to bug 191652 which is fixed in HEAD for 3.4 and will be fixed in 3.3.1. But I do not think this is the bug you are seeing because it does not sound like you actually updated your bundle's content. Instead it seems you are updating the bundle simply to trigger a reload of the library. Can you provide more information to reproduce?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
