[
https://issues.apache.org/jira/browse/SLING-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370306#comment-14370306
]
Oliver Lietz commented on SLING-4223:
-------------------------------------
I still don't like the whiteboard and prefer using
{{org.apache.sling.commons.osgi.SortingServiceTracker}}. This allows adding
content readers for JSON, XML and ZIP/JAR and order them with service ranking
also: http://svn.apache.org/viewvc/sling/whiteboard/olli/contentloader/
I've also added a basic sample (SLING-4526):
http://svn.apache.org/viewvc/sling/trunk/samples/org.apache.sling.samples.jcr.contentloader/
There is still some clean up, documentation, testing and optimization to do.
[~bruceedge], is there anything missing to make it work for you?
> Make Content Loader extensible to support new import formats
> ------------------------------------------------------------
>
> Key: SLING-4223
> URL: https://issues.apache.org/jira/browse/SLING-4223
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR ContentLoader 2.1.10
> Reporter: Oliver Lietz
> Assignee: Tomek Rękawek
> Fix For: JCR ContentLoader 2.2.0
>
> Attachments: SLING-4223.patch
>
>
> The current Content Loader supports a basic set of import formats which are
> identified by extension: {{.xml}}, {{.jcr.xml}}, {{.json}}, {{.jar}} and
> {{.zip}}.
> There is a [user
> request|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%3cd0a6198c.20fbeb%[email protected]%3e]
> to support custom formats like Adobe Folio and [some ideas how to
> implement|http://mail-archives.apache.org/mod_mbox/sling-users/201412.mbox/%[email protected]%3e]:
> * we create a new org.apache.sling.contentloader.reader package to be
> exported at version 1.0
> * move the ContentCreator (@ProviderType) and ContentReader (@ConsumerType)
> to that new package
> * convert the BaseImportLoader into a standalone ContentReader service holder
> used by the DefaultContentImporter and ContentLoaderService components.
> * For the ContentReader service interface we define service registration
> properties for the service to expose the file name extension (and maybe
> content type) the reader supports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
