[
https://issues.apache.org/jira/browse/SLING-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989608#comment-16989608
]
Carsten Ziegeler commented on SLING-8877:
-----------------------------------------
[~kwin] I'm not sure what you are refering to with changes in bundle location.
The OSGi spec defines that the bundle location never changes on bundle update.
So the OSGi controller can only influence the location on first install of a
bundle, but not afterwards.
Yes, my suggestion is that the osgi installer basically sets a URL using a new
scheme like osgiinstaller, the path of that URL probably contains the id of the
bundle (symbolic name) without version. When the url handler resolves this it
can use information from the osgi installer and look at the currently installed
version and do whatever magic is needed. It can find out from where that bundle
came initially.
Write back is not supported for bundles, but even if, with the above described
mechanism it still should be possible to do that correctly. All the required
information is 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
