You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2018/12/13 16:50:00 UTC
[jira] [Updated] (SLING-8116) ValueMap - implement default methods
using OSGI Converter
[ https://issues.apache.org/jira/browse/SLING-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu updated SLING-8116:
--------------------------------
Fix Version/s: (was: API 2.18.6)
API 2.20.2
> ValueMap - implement default methods using OSGI Converter
> ---------------------------------------------------------
>
> Key: SLING-8116
> URL: https://issues.apache.org/jira/browse/SLING-8116
> Project: Sling
> Issue Type: Improvement
> Reporter: Jason E Bailey
> Assignee: Jason E Bailey
> Priority: Major
> Fix For: API 2.20.2
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Implement default methods in the ValueMap interface that leverages the OSGi Converter
> see
> [https://osgi.org/specification/osgi.cmpn/7.0.0/util.converter.html]
> Once this is implemented, custom implementations of the ValueMap interface can start being removed, where appropriate, so that a consistent and comprehensive conversion of properties occur. We can then add new Rules to the Converter to allow features to be populated to all ValueMap implementations.
>
> To implement this, the following will also need to happen
> * The Converter bundle will need to be added as a required bundle
> ** Various scripts that define the minimum needed set of bundles will need to be updated
> * Communication on the difference in behaviour between the current ValueMap and the ValueMap with Converter
> * Although not within the Maven definition. org.osgi.util.Function needs to be available as well for the Converter to initiate correctly.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)