[ 
https://issues.apache.org/jira/browse/SLING-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407455#comment-15407455
 ] 

Tommaso Teofili edited comment on SLING-5815 at 8/4/16 9:10 AM:
----------------------------------------------------------------

bq. The thing is that path mapping might be more difficult to support as the 
serialization format might be hierarchical and mapping to another tree might 
break the format

[~mpetria] what do you mean exactly ?

I think I prefer the idea of the {{ResourceMapper}} because it's basically 
transforming {{Resources}}. I think it's important to understand what's the 
usage of such mappers, in my view they can be used to:
- filter undesired properties at export/import time
- expand the path of a resource to sit under a certain subtree, e.g. for multi 
tenant receivers
- other ?

Or would you want to use such mappers also to substitute the current filtering 
based on information in {{DistributionRequest}} ? 

 


was (Author: teofili):
bq. The thing is that path mapping might be more difficult to support as the 
serialization format might be hierarchical and mapping to another tree might 
break the format

[~mpetria] what do you mean exactly ?

I think I prefer the idea of the {{ResourceMapper}} because it's basically 
transforming {{Resources}}, which I think is the idea behind that, right ? As 
it's important to understand what's the usage of such mappers, in my view they 
can be used to:
- filter undesired properties at export/import time
- expand the path of a resource to sit under a certain subtree, e.g. for multi 
tenant receivers

Or would you want to use such mappers also to substitute the current filtering 
based on information in {{DistributionRequest}} ? 

 

> 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
>
>
> 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)

Reply via email to