[RFC]the OSGi semantics of bundle uninstall. #554
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The behavior of the
uninstall()
method of Bundle interface is specified as follows:Clearly, the current implementation, which is introduced by #476, does not touch persistent storage.
As seen in
TEST_F(CxxBundleArchiveTestSuite, BundleArchiveReusedTest)
, after uninstall, the bundle archive is intact.The previous implementation does set the bundle's persistent state to UNINSTALLED, but does nothing more than that.
Therefore, both are incorrect.
This PR tries to implement the correct behavior without affecting
framework_shutdown
.