You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2016/12/20 21:02:58 UTC

[jira] [Assigned] (SLING-6420) Enhance Conversion Rules for ValueMapDecorator

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

Stefan Seifert reassigned SLING-6420:
-------------------------------------

    Assignee: Stefan Seifert

> Enhance Conversion Rules for ValueMapDecorator
> ----------------------------------------------
>
>                 Key: SLING-6420
>                 URL: https://issues.apache.org/jira/browse/SLING-6420
>             Project: Sling
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: API 2.16.2
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>             Fix For: API 2.16.4
>
>
> background in this discussion in the [mailing list|https://lists.apache.org/thread.html/696deaf2f6b67d99ee969aad19e5b8b00d9c53c78e9ad75633e9e809@%3Cdev.sling.apache.org%3E] the conversion rules of the ValueMapDecorator should be unified with the conversion rules of the JCR ValueMap implement (as long as they are not too JCR specific).
> the conversion rules that are currently supported are outlined here: https://cwiki.apache.org/confluence/x/OQkIB
> with this ticket we want to add support for
> * Convert any number type of (Long, Byte, Short, Integer, Double, Float, BigDecimal) -> to each of them or String and vice versa
> * Convert any date type of (Calendar, Date) -> to each of them or String and vice versa
> * and make the existing implementation a bit more efficient (avoid string parsing when possible)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)