Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
3.4
-
None
-
Unit
-
Description
Here is an example of what's happening right now:
- register the component A with role R and hint H
- register the component B with role R and hint H
- unregister the component B
- there is no component anymore with role R and hint H, A is lost even if it has never been officially unregistered
In a larger use case what this mean is that you can, in XWiki, install an extension which overwrite some standard component like the XHTML renderer to extend it and when you uninstall the extension you ends up with no XHTML renderer which makes XWiki pretty much unusable...
We could make each role/hint couple have a stack of descriptors assigned to it instead of a single descriptor so that we can restore the previous component when unregistering the current one.
Attachments
Issue Links
- causes
-
XPRISMJS-13 Uninstalling Prism.js Code Macro Replacement doesn't restore the standard Code Macro until XWiki is restarted
-
- Open
-
- is related to
-
XCOMMONS-3845 Components declared with a priority in components.txt are not unregistered when uninstalling a JAR extension
-
- Closed
-
- links to