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-8897) WebConsole for OSGi configuration serialization
Date Sat, 04 Jan 2020 17:30:00 GMT

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

Konrad Windszus updated SLING-8897:
-----------------------------------
    Fix Version/s: Installer Console 1.0.4

> WebConsole for OSGi configuration serialization
> -----------------------------------------------
>
>                 Key: SLING-8897
>                 URL: https://issues.apache.org/jira/browse/SLING-8897
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>    Affects Versions: Installer Core 3.9.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Installer Console 1.0.4, Installer Core 3.9.2
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Currently the serialization of OSGi configuration can be achieved via the write back
mechanism of the different providers. As very often the location is read-only and also there
are different serialization formats (https://sling.apache.org/documentation/bundles/configuration-installer-factory.html)
it would be reasonable to instead provide a central web console via the OSGi Installer Core
which allows to emit different serialization format per configuration PID. The output is only
via HTML.
> That way the same serialization logic only needs to be implemented once (instead of multiple
times) and the emitted config serialization can be put easily into the SCM files via copy&paste.



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

Mime
View raw message