You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/05/13 17:07:15 UTC

[jira] [Commented] (SLING-3556) The Filter API should work on resources, not on filesystem-based paths

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

Robert Munteanu commented on SLING-3556:
----------------------------------------

Attached [^SLING-3556-wip-1.patch], which shows how this API can look.

> The Filter API should work on resources, not on filesystem-based paths
> ----------------------------------------------------------------------
>
>                 Key: SLING-3556
>                 URL: https://issues.apache.org/jira/browse/SLING-3556
>             Project: Sling
>          Issue Type: Improvement
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.0
>            Reporter: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.0.2
>
>         Attachments: SLING-3556-wip-1.patch
>
>
> Today the SlingLaunchpadBehaviour encapsulates lot of knowledge about what it takes to find out if a resource should be filtered or not ( also visited in the context of SLING-3112 ). This knowledge should be rooted in the Filter API, which currently takes paths. 
> Instead, it should take a ResourceProxy instance, and delegate to the SerializationKindManager to see what the serialization policy is, so that it can determine the repository path.



--
This message was sent by Atlassian JIRA
(v6.2#6252)