[SLING-8877] Register URL Handler for JCR Installer scheme (jcrinstall)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Installer Core 3.9.0
• Fix Version/s: Installer Core 3.10.0
• Component/s: Installer
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 05/Dec/19 13:34
• Updated: 25/Feb/20 08:03
• Resolved: 06/Dec/19 19:16

Description

As outlined in https://lists.apache.org/thread.html/7ee96284d6a35d75523ab73ed801d87f22507ce1e13dd05c6afa7308%401411908283%40%3Cusers.sling.apache.org%3E there is the edge case where the bundle location is being used to look up the original source code. To allow that in the context of bundles deployed via the JCR Installer, one should register a custom URL handler for scheme jcrinstall via the means of https://osgi.org/specification/osgi.core/7.0.0/service.url.html#d0e42987. Similarly for all other providers.

Issue Links

• breaks: SLING-9139 URLHandler unregistered too often
• relates to: FELIX-5204 IllegalStateException when using custom URL handlers for bundles
• relates to: SLING-4747 Installer does not consistently update bundle location in Webconsole
• relates to: FELIX-4658 URL of the CodeSource of a ProtectionDomain should resolve to the right JAR
• links to: GitHub Pull Request #2
• links to: GitHub Pull Request #4