You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/08/10 09:52:14 UTC

[jira] Created: (SLING-1077) Try to encode map keys for value map implementations

Try to encode map keys for value map implementations
----------------------------------------------------

                 Key: SLING-1077
                 URL: https://issues.apache.org/jira/browse/SLING-1077
             Project: Sling
          Issue Type: Improvement
          Components: JCR Resource
    Affects Versions: JCR Webdav 2.0.4
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
             Fix For: JCR Resource 2.0.6


The current value map implementations (JcrPropertyMap and JrModifiablePropertyMap) try to directly use the provided map key as a property name. If the name contains illegal characters (for a JCR) then setting/getting these properties fails.
Therefore an encoding should be used to avoid these cases.
We'll use the ISO9075 encoding as a start. Adding this encoding should be compatible to the current implementation as it just adds new use cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SLING-1077) Try to encode map keys for value map implementations

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated SLING-1077:
------------------------------------

    Affects Version/s:     (was: JCR Webdav 2.0.4)
                       JCR Resource 2.0.4

> Try to encode map keys for value map implementations
> ----------------------------------------------------
>
>                 Key: SLING-1077
>                 URL: https://issues.apache.org/jira/browse/SLING-1077
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR Resource
>    Affects Versions: JCR Resource 2.0.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Resource 2.0.6
>
>
> The current value map implementations (JcrPropertyMap and JrModifiablePropertyMap) try to directly use the provided map key as a property name. If the name contains illegal characters (for a JCR) then setting/getting these properties fails.
> Therefore an encoding should be used to avoid these cases.
> We'll use the ISO9075 encoding as a start. Adding this encoding should be compatible to the current implementation as it just adds new use cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (SLING-1077) Try to encode map keys for value map implementations

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-1077.
-----------------------------------

    Resolution: Fixed

Encode keys with ISO9075 - updated tests in Revision: 802684

> Try to encode map keys for value map implementations
> ----------------------------------------------------
>
>                 Key: SLING-1077
>                 URL: https://issues.apache.org/jira/browse/SLING-1077
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR Resource
>    Affects Versions: JCR Resource 2.0.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: JCR Resource 2.0.6
>
>
> The current value map implementations (JcrPropertyMap and JrModifiablePropertyMap) try to directly use the provided map key as a property name. If the name contains illegal characters (for a JCR) then setting/getting these properties fails.
> Therefore an encoding should be used to avoid these cases.
> We'll use the ISO9075 encoding as a start. Adding this encoding should be compatible to the current implementation as it just adds new use cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.