You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Vidar S. Ramdal (JIRA)" <ji...@apache.org> on 2009/10/22 19:42:59 UTC

[jira] Created: (SLING-1161) Easier initial content loading of binary files

Easier initial content loading of binary files
----------------------------------------------

                 Key: SLING-1161
                 URL: https://issues.apache.org/jira/browse/SLING-1161
             Project: Sling
          Issue Type: New Feature
          Components: JCR
    Affects Versions: JCR Contentloader 2.0.4
            Reporter: Vidar S. Ramdal
            Priority: Minor
             Fix For: JCR Contentloader 2.0.6


When specifying initial content in XML file(s), and you want to include binary files somwhere in your content structure, you currently have 2 options:
1: Inline the binary data in the XML file (like you get when you do a JCR export)
2: Create a folder structure next to the XML file, and store your binary files in the corresponding folders

Option 1 is not suitable for files over a certain size, and option 2 is a royal pain when you have a deep structure, and also takes away some of the advantages of specifying content in XML.

Therefore, I suggest the option of storing your binary file anywhere, while referencing it in your XML. When the content loader (o.a.s.jcr.contentloader.i.r.XmlReader) encounters such a reference, it calls ContentCreator.createFileAndResourceNode so that the file is loaded to the correct place.

Patch coming up.

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


[jira] Closed: (SLING-1161) Easier initial content loading of binary files

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

Carsten Ziegeler closed SLING-1161.
-----------------------------------


> Easier initial content loading of binary files
> ----------------------------------------------
>
>                 Key: SLING-1161
>                 URL: https://issues.apache.org/jira/browse/SLING-1161
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>    Affects Versions: JCR Contentloader 2.0.4
>            Reporter: Vidar S. Ramdal
>            Assignee: Vidar S. Ramdal
>            Priority: Minor
>             Fix For: JCR Contentloader 2.0.6
>
>         Attachments: SLING-1161.patch
>
>
> When specifying initial content in XML file(s), and you want to include binary files somwhere in your content structure, you currently have 2 options:
> 1: Inline the binary data in the XML file (like you get when you do a JCR export)
> 2: Create a folder structure next to the XML file, and store your binary files in the corresponding folders
> Option 1 is not suitable for files over a certain size, and option 2 is a royal pain when you have a deep structure, and also takes away some of the advantages of specifying content in XML.
> Therefore, I suggest the option of storing your binary file anywhere, while referencing it in your XML. When the content loader (o.a.s.jcr.contentloader.i.r.XmlReader) encounters such a reference, it calls ContentCreator.createFileAndResourceNode so that the file is loaded to the correct place.
> Patch coming up.

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


Re: [jira] Resolved: (SLING-1161) Easier initial content loading of binary files

Posted by Vidar Ramdal <vi...@idium.no>.
>>                 Key: SLING-1161
>>                 URL: https://issues.apache.org/jira/browse/SLING-1161

On Tue, Oct 27, 2009 at 9:49 PM, Mike Müller <mi...@mysign.ch> wrote:
> I like this extension, except for the default of the last modified
> date which will be set to the current date if the attribute lastModified
> is not set. IMHO it would be better to take the last modified date of
> the binary itself in this case than the current date.

You're right, of course - why didn't I think of that? (smacking my forehead).
=> https://issues.apache.org/jira/browse/SLING-1165

-- 
Vidar S. Ramdal <vi...@idium.no> - http://www.idium.no
Sommerrogata 13-15, N-0255 Oslo, Norway
+ 47 22 00 84 00 / +47 21 531941, ext 2070

RE: [jira] Resolved: (SLING-1161) Easier initial content loading of binary files

Posted by Mike Müller <mi...@mysign.ch>.
Hi Vidar

I like this extension, except for the default of the last modified
date which will be set to the current date if the attribute lastModified
is not set. IMHO it would be better to take the last modified date of
the binary itself in this case than the current date.

best regards
mike

> -----Original Message-----
> From: Vidar S. Ramdal (JIRA) [mailto:jira@apache.org]
> Sent: Tuesday, October 27, 2009 10:47 AM
> To: dev@sling.apache.org
> Subject: [jira] Resolved: (SLING-1161) Easier initial content
> loading of
> binary files
>
>
>
>      [
> https://issues.apache.org/jira/browse/SLING-1161?page=com.atla
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vidar S. Ramdal resolved SLING-1161.
------------------------------------

    Resolution: Fixed
      Assignee: Vidar S. Ramdal

Patch applied in rev#830106

> Easier initial content loading of binary files
> ----------------------------------------------
>
>                 Key: SLING-1161
>                 URL: https://issues.apache.org/jira/browse/SLING-1161
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>    Affects Versions: JCR Contentloader 2.0.4
>            Reporter: Vidar S. Ramdal
>            Assignee: Vidar S. Ramdal
>            Priority: Minor
>             Fix For: JCR Contentloader 2.0.6
>
>         Attachments: SLING-1161.patch
>
>
> When specifying initial content in XML file(s), and you want to include binary files somwhere in your content structure, you currently have 2 options:
> 1: Inline the binary data in the XML file (like you get when you do a JCR export)
> 2: Create a folder structure next to the XML file, and store your binary files in the corresponding folders
> Option 1 is not suitable for files over a certain size, and option 2 is a royal pain when you have a deep structure, and also takes away some of the advantages of specifying content in XML.
> Therefore, I suggest the option of storing your binary file anywhere, while referencing it in your XML. When the content loader (o.a.s.jcr.contentloader.i.r.XmlReader) encounters such a reference, it calls ContentCreator.createFileAndResourceNode so that the file is loaded to the correct place.
> Patch coming up.

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


[jira] Resolved: (SLING-1161) Easier initial content loading of binary files

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

Vidar S. Ramdal resolved SLING-1161.
------------------------------------

    Resolution: Fixed
      Assignee: Vidar S. Ramdal

Patch applied in rev#830106

> Easier initial content loading of binary files
> ----------------------------------------------
>
>                 Key: SLING-1161
>                 URL: https://issues.apache.org/jira/browse/SLING-1161
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>    Affects Versions: JCR Contentloader 2.0.4
>            Reporter: Vidar S. Ramdal
>            Assignee: Vidar S. Ramdal
>            Priority: Minor
>             Fix For: JCR Contentloader 2.0.6
>
>         Attachments: SLING-1161.patch
>
>
> When specifying initial content in XML file(s), and you want to include binary files somwhere in your content structure, you currently have 2 options:
> 1: Inline the binary data in the XML file (like you get when you do a JCR export)
> 2: Create a folder structure next to the XML file, and store your binary files in the corresponding folders
> Option 1 is not suitable for files over a certain size, and option 2 is a royal pain when you have a deep structure, and also takes away some of the advantages of specifying content in XML.
> Therefore, I suggest the option of storing your binary file anywhere, while referencing it in your XML. When the content loader (o.a.s.jcr.contentloader.i.r.XmlReader) encounters such a reference, it calls ContentCreator.createFileAndResourceNode so that the file is loaded to the correct place.
> Patch coming up.

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


[jira] Updated: (SLING-1161) Easier initial content loading of binary files

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

Vidar S. Ramdal updated SLING-1161:
-----------------------------------

    Attachment: SLING-1161.patch

Patch + testcase

> Easier initial content loading of binary files
> ----------------------------------------------
>
>                 Key: SLING-1161
>                 URL: https://issues.apache.org/jira/browse/SLING-1161
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>    Affects Versions: JCR Contentloader 2.0.4
>            Reporter: Vidar S. Ramdal
>            Priority: Minor
>             Fix For: JCR Contentloader 2.0.6
>
>         Attachments: SLING-1161.patch
>
>
> When specifying initial content in XML file(s), and you want to include binary files somwhere in your content structure, you currently have 2 options:
> 1: Inline the binary data in the XML file (like you get when you do a JCR export)
> 2: Create a folder structure next to the XML file, and store your binary files in the corresponding folders
> Option 1 is not suitable for files over a certain size, and option 2 is a royal pain when you have a deep structure, and also takes away some of the advantages of specifying content in XML.
> Therefore, I suggest the option of storing your binary file anywhere, while referencing it in your XML. When the content loader (o.a.s.jcr.contentloader.i.r.XmlReader) encounters such a reference, it calls ContentCreator.createFileAndResourceNode so that the file is loaded to the correct place.
> Patch coming up.

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


[jira] Updated: (SLING-1161) Easier initial content loading of binary files

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

Vidar S. Ramdal updated SLING-1161:
-----------------------------------

    Attachment:     (was: SLING-1161.patch)

> Easier initial content loading of binary files
> ----------------------------------------------
>
>                 Key: SLING-1161
>                 URL: https://issues.apache.org/jira/browse/SLING-1161
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>    Affects Versions: JCR Contentloader 2.0.4
>            Reporter: Vidar S. Ramdal
>            Priority: Minor
>             Fix For: JCR Contentloader 2.0.6
>
>         Attachments: SLING-1161.patch
>
>
> When specifying initial content in XML file(s), and you want to include binary files somwhere in your content structure, you currently have 2 options:
> 1: Inline the binary data in the XML file (like you get when you do a JCR export)
> 2: Create a folder structure next to the XML file, and store your binary files in the corresponding folders
> Option 1 is not suitable for files over a certain size, and option 2 is a royal pain when you have a deep structure, and also takes away some of the advantages of specifying content in XML.
> Therefore, I suggest the option of storing your binary file anywhere, while referencing it in your XML. When the content loader (o.a.s.jcr.contentloader.i.r.XmlReader) encounters such a reference, it calls ContentCreator.createFileAndResourceNode so that the file is loaded to the correct place.
> Patch coming up.

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


[jira] Updated: (SLING-1161) Easier initial content loading of binary files

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

Vidar S. Ramdal updated SLING-1161:
-----------------------------------

    Attachment: SLING-1161.patch

Updated patch

> Easier initial content loading of binary files
> ----------------------------------------------
>
>                 Key: SLING-1161
>                 URL: https://issues.apache.org/jira/browse/SLING-1161
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>    Affects Versions: JCR Contentloader 2.0.4
>            Reporter: Vidar S. Ramdal
>            Priority: Minor
>             Fix For: JCR Contentloader 2.0.6
>
>         Attachments: SLING-1161.patch, SLING-1161.patch
>
>
> When specifying initial content in XML file(s), and you want to include binary files somwhere in your content structure, you currently have 2 options:
> 1: Inline the binary data in the XML file (like you get when you do a JCR export)
> 2: Create a folder structure next to the XML file, and store your binary files in the corresponding folders
> Option 1 is not suitable for files over a certain size, and option 2 is a royal pain when you have a deep structure, and also takes away some of the advantages of specifying content in XML.
> Therefore, I suggest the option of storing your binary file anywhere, while referencing it in your XML. When the content loader (o.a.s.jcr.contentloader.i.r.XmlReader) encounters such a reference, it calls ContentCreator.createFileAndResourceNode so that the file is loaded to the correct place.
> Patch coming up.

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