On Mon, Sep 19, 2011 at 9:51 AM, Vidar Ramdal <vidar.ram...@webstep.no> wrote: >> 2011/9/19 Felix Meschberger <fmesc...@adobe.com>: >>> How about: >>> >>> * Creating a separate bundle taking this servlet >> Yeah, that's an option - though if noone needs it, we could as well remove >> it :) >> >>> * Use the request's resource path as a final filter when dumping the >>> result ? > > 2011/9/19 Carsten Ziegeler <cziege...@apache.org>: >> Sure, that's possible but again if noone is using this anyway, way >> spending time in this one :) > > Well, I do know that my former employer Idium is using it. > But then, anyone is free to take the existing code and package it in a > self-made bundle, I guess.
I use it daily :) I agree that the way the resource is effectively ignored is a bit confusing, but this does seem like a useful feature. Without looking at the details, how about we create a new "query" bundle which has a backwards-compatible selector-based servlet which is disabled by default and a new servlet (/bin/query?) which uses an object return type to meet Antonio's concerns about returning a JSON array. Alternatively, the selector-based servlet could be modified to take the path into account when configured to do so. WDYT? Justin > > -- > Vidar S. Ramdal <vidar.ram...@webstep.no> > Webstep AS - http://www.webstep.no > Besøksadresse: Lilleakerveien 8, 0283 Oslo > Postadresse: Postboks 272 Lilleaker, 0216 Oslo >
