sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (Jira)" <j...@apache.org>
Subject [jira] [Updated] (SLING-8877) Register URL Handler for JCR Installer scheme (jcrinstall)
Date Fri, 06 Dec 2019 11:41:00 GMT

     [ https://issues.apache.org/jira/browse/SLING-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Konrad Windszus updated SLING-8877:
-----------------------------------
    Affects Version/s:     (was: JCR Installer 3.1.26)
                       Installer Core 3.9.0

> 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: Installer Core 3.9.0
>            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.
Similarly for all other providers.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message