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

Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2014/05/01 15:22:15 UTC

[jira] [Updated] (SLING-2226) Move json query servlet to a new compat bundle

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

Bertrand Delacretaz updated SLING-2226:
---------------------------------------

    Description: 
As discussed in the mailing list (http://markmail.org/message/sxurvywelnyt3ntz), we should move the query servlet into a separate module as in general we discourage the use of it
For one, it is a strange thing as it applies to any resource path when ".query.json" is appended although the resource path is not used at all and the second reason is, that this can lead to potential missuses of this feature.

  was:
As discussed in the mailing list, we should move the query servlet into a separate module as in general we discourage the use of it
For one, it is a strange thing as it applies to any resource path when ".query.json" is appended although the resource path is not used at all and the second reason is, that this can lead to potential missuses of this feature.


> Move json query servlet to a new compat bundle
> ----------------------------------------------
>
>                 Key: SLING-2226
>                 URL: https://issues.apache.org/jira/browse/SLING-2226
>             Project: Sling
>          Issue Type: Task
>          Components: Servlets
>    Affects Versions: Servlets Get 2.1.2
>            Reporter: Carsten Ziegeler
>            Assignee: Bertrand Delacretaz
>             Fix For: Servlets Get 2.1.4, Servlets Compat 1.0.0
>
>
> As discussed in the mailing list (http://markmail.org/message/sxurvywelnyt3ntz), we should move the query servlet into a separate module as in general we discourage the use of it
> For one, it is a strange thing as it applies to any resource path when ".query.json" is appended although the resource path is not used at all and the second reason is, that this can lead to potential missuses of this feature.



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