You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2013/09/23 15:46:02 UTC

[jira] [Updated] (SLING-3089) Investigate using the same model between the repository sync and the Sling (JCR) content provider

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

Robert Munteanu updated SLING-3089:
-----------------------------------

    Component/s: IDE
    
> Investigate using the same model between the repository sync and the Sling (JCR) content provider
> -------------------------------------------------------------------------------------------------
>
>                 Key: SLING-3089
>                 URL: https://issues.apache.org/jira/browse/SLING-3089
>             Project: Sling
>          Issue Type: Improvement
>          Components: IDE
>            Reporter: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.0.2
>
>
> If we use the same data model we can benefit from the same code base. Right now there's some duplication and we potentially miss fixes from one area from another. For instance, the content provider does not yet support properties stored in $(nodeName).dir/.content.xml files.
> Also, it would help in formalizing the SerializationManager API even more.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira