[
https://issues.apache.org/jira/browse/SLING-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988839#comment-16988839
]
Konrad Windszus commented on SLING-8877:
----------------------------------------
The problem is that the bundle location is no longer updated with each update,
therefore the jcrinstall url might not point to an existing path.
[~cziegeler] As Apache Felix is relying on the bundle location for getting the
ProtectionDomain's CodeSource, this behaviour leads to issues e.g. when some
code is looking up the code from there.
> Register URL Handler for JCR Installer scheme (jcrinstall)
> ----------------------------------------------------------
>
> Key: SLING-8877
> URL: https://issues.apache.org/jira/browse/SLING-8877
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: JCR Installer 3.1.26
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: JCR Installer 3.1.28
>
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
