Am 15.06.15 um 11:15 schrieb Bertrand Delacretaz: > On Mon, Jun 15, 2015 at 10:57 AM, Carsten Ziegeler <cziege...@apache.org> > wrote: >> Am 15.06.15 um 10:44 schrieb Bertrand Delacretaz: >> ...I have not seen any compelling reason to not do it and the >> advantages outweight the potential disadvantages... > > I'm not saying we should "not do it", and as you rightly say there's > no better concrete proposal than yours at the moment. But we are > introducing a new API in our core without (most of us) being really > convinced about it, and this is not good. It really seems that people who are not convinced have never felt the current pain - while people who are on the pro side exactly felt this pain and ran into the problems which this is trying to solve. I'm absolutely unsure on how to solve that situation.
> > Modularizing is our usual answer to such situations, to keep a bit of > flexibility if we change our minds later on. > > You say we cannot put the query API in a separate bundle because "we > need provider support", can you elaborate? I don't see what exactly > prevents the org.apache.sling.api.resource.query package from being > provided by a different bundle - but maybe I missed something. The query api is the user api, right this can be moved into a different bundle. But of course the interesting part is the implementation and this is part of the new provider spi which references this api. A provider does the query and therefore needs access to the query object etc. I just put the query client api into a separate package as the resource package is overloaded already. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
