You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2008/01/25 03:18:34 UTC

[jira] Created: (SLING-195) use system view format for XML resource loader

use system view format for XML resource loader
----------------------------------------------

                 Key: SLING-195
                 URL: https://issues.apache.org/jira/browse/SLING-195
             Project: Sling
          Issue Type: Improvement
          Components: Repository
            Reporter: Tobias Bocanegra


the current org.apache.sling.jcr.resource.internal.loader.XmlReader has a pretty simple format for loading content from the bundles into the repository. the pain is that if you already have repository content, you can't create just a SysView export and put it in the resources.

suggest to change the XmlReader to accept a Sysview dump as provided by a system view content export.


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


[jira] Assigned: (SLING-195) use system view format for XML resource loader

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

Felix Meschberger reassigned SLING-195:
---------------------------------------

    Assignee: Felix Meschberger

> use system view format for XML resource loader
> ----------------------------------------------
>
>                 Key: SLING-195
>                 URL: https://issues.apache.org/jira/browse/SLING-195
>             Project: Sling
>          Issue Type: Improvement
>          Components: Repository
>            Reporter: Tobias Bocanegra
>            Assignee: Felix Meschberger
>
> the current org.apache.sling.jcr.resource.internal.loader.XmlReader has a pretty simple format for loading content from the bundles into the repository. the pain is that if you already have repository content, you can't create just a SysView export and put it in the resources.
> suggest to change the XmlReader to accept a Sysview dump as provided by a system view content export.

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


[jira] Commented: (SLING-195) use system view format for XML resource loader

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562470#action_12562470 ] 

Felix Meschberger commented on SLING-195:
-----------------------------------------

While I agree, that it would be nice to have sysview support, creating sysview manually is more than just pain :-) So I suggest we investigate whether it would be possible to support support sysview in addition to what we have...

> use system view format for XML resource loader
> ----------------------------------------------
>
>                 Key: SLING-195
>                 URL: https://issues.apache.org/jira/browse/SLING-195
>             Project: Sling
>          Issue Type: Improvement
>          Components: Repository
>            Reporter: Tobias Bocanegra
>
> the current org.apache.sling.jcr.resource.internal.loader.XmlReader has a pretty simple format for loading content from the bundles into the repository. the pain is that if you already have repository content, you can't create just a SysView export and put it in the resources.
> suggest to change the XmlReader to accept a Sysview dump as provided by a system view content export.

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


[jira] Commented: (SLING-195) use system view format for XML resource loader

Posted by "Tobias Bocanegra (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562473#action_12562473 ] 

Tobias Bocanegra commented on SLING-195:
----------------------------------------

good point. but then would 'docview' be a better option. or allow both.

the fact is, that there are standardized XML serializations defined in jsr170 that also have export/import support in the api. so we should make use of them.

> use system view format for XML resource loader
> ----------------------------------------------
>
>                 Key: SLING-195
>                 URL: https://issues.apache.org/jira/browse/SLING-195
>             Project: Sling
>          Issue Type: Improvement
>          Components: Repository
>            Reporter: Tobias Bocanegra
>
> the current org.apache.sling.jcr.resource.internal.loader.XmlReader has a pretty simple format for loading content from the bundles into the repository. the pain is that if you already have repository content, you can't create just a SysView export and put it in the resources.
> suggest to change the XmlReader to accept a Sysview dump as provided by a system view content export.

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


[jira] Resolved: (SLING-195) use system view format for XML resource loader

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

Felix Meschberger resolved SLING-195.
-------------------------------------

    Resolution: Fixed

Implement support for system view XML import in Rev. 619470.

For an XML file to be accepted as system view, the name of the file must end with ".jcr.xml". Otherwise, if the extension is just ".xml", the oldstyle, non-standard import format is assumed and checked. This separation with a special extension also allows for the less problematic import of plain XML files without them being first tried to be imported as system view and possibly leaving garbage.

> use system view format for XML resource loader
> ----------------------------------------------
>
>                 Key: SLING-195
>                 URL: https://issues.apache.org/jira/browse/SLING-195
>             Project: Sling
>          Issue Type: Improvement
>          Components: Repository
>            Reporter: Tobias Bocanegra
>            Assignee: Felix Meschberger
>
> the current org.apache.sling.jcr.resource.internal.loader.XmlReader has a pretty simple format for loading content from the bundles into the repository. the pain is that if you already have repository content, you can't create just a SysView export and put it in the resources.
> suggest to change the XmlReader to accept a Sysview dump as provided by a system view content export.

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


[jira] Closed: (SLING-195) use system view format for XML resource loader

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

Tobias Bocanegra closed SLING-195.
----------------------------------


thanks.

> use system view format for XML resource loader
> ----------------------------------------------
>
>                 Key: SLING-195
>                 URL: https://issues.apache.org/jira/browse/SLING-195
>             Project: Sling
>          Issue Type: Improvement
>          Components: Repository
>            Reporter: Tobias Bocanegra
>            Assignee: Felix Meschberger
>
> the current org.apache.sling.jcr.resource.internal.loader.XmlReader has a pretty simple format for loading content from the bundles into the repository. the pain is that if you already have repository content, you can't create just a SysView export and put it in the resources.
> suggest to change the XmlReader to accept a Sysview dump as provided by a system view content export.

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