[ 
https://issues.apache.org/jira/browse/SLING-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989468#comment-16989468
 ] 

Konrad Windszus edited comment on SLING-8877 at 12/6/19 7:19 AM:
-----------------------------------------------------------------

[~cziegeler] Can you elaborate a bit on that? You mean that the OSGi installer 
is supposed to set the bundle location to some other url instead of the scheme 
+ id provided by the provider? And that this URL should have the common scheme 
osgiinstaller? I guess then the update handling does not really work well, 
because then the write back will not notify the right provider. Maybe I am 
missing something here though.

For me it just sounds like the easiest solution to always update the bundle 
location to the current scheme + prefix. Why has that behaviour been changed in 
the past?


was (Author: kwin):
[~cziegeler] Can you elaborate a bit on that? You mean that the OSGi installer 
is supposed to set the bundle location to some other url instead of the scheme 
+ id provided by the provider? And that this URL should have the common scheme 
osgiinstaller? I guess then the update handling does not really work well, 
because then the write back will not notify the right provider. Maybe I am 
missing something here though.

> 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)

Reply via email to