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

Bertrand Delacretaz commented on SLING-2226:
--------------------------------------------

To clarifiy how people can use the JsonQueryServlet after this change: it is 
now provided by the org.apache.sling.servlets.compat bundle, source code at 
https://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/compat

We haven't released that bundle yet, I'll do that as soon as I find some time - 
for now people can build it themselves. The  JsonQueryServletTest [1] provides 
some usage examples.

[1] 
https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/JsonQueryServletTest.java



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

Reply via email to