[jira] [Updated] (SLING-5815) Expose DistributionContentSerializer

["Tommaso Teofili (JIRA)" <ji...@apache.org>]

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

Tommaso Teofili updated SLING-5815:
-----------------------------------
    Attachment: SLING-5815.1.patch

attached additional draft patch (for distribution.core only) with {{DistributionExportOptions}} holding a {{DistributionExportFilter}}.
The good part of this approach is that the resource tree is not traversed before serialization happens, it mimics a bit the VLT filters, but can be reused for other formats without introducing a dependency on VLT. The not so good part is that for {{FileVaultContentSerializer}} it requires to remap the {{DistributionExportFilter}} into a {{WorkspaceFilter}}; as a mitigation we could keep the {{DistributionRequest}} inside the {{DistributionExportOptions}} so that VLT serialization can better leverage that while other formats would use the information contained in the {{DistributionExportFIlter}}.

Not going the {{ResourceMapper}} way until we can clarify a bit further expected usage.

> Expose DistributionContentSerializer 
> -------------------------------------
>
>                 Key: SLING-5815
>                 URL: https://issues.apache.org/jira/browse/SLING-5815
>             Project: Sling
>          Issue Type: Improvement
>          Components: Distribution
>            Reporter: Tommaso Teofili
>            Assignee: Tommaso Teofili
>             Fix For: Content Distribution 0.2.0
>
>         Attachments: SLING-5815.0.patch, SLING-5815.1.patch
>
>
> Expose {{DistributionContentSerializer}} API from _org.apache.sling.distribution.core_ in order to allow implementation of custom serialization formats (e.g. Avro and Kryo defined in _org.apache.sling.distribution.extensions_).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)