Hello Bertrand, On Mon, Jan 26, 2015 at 11:02 AM, Bertrand Delacretaz < [email protected]> wrote: > > I have commented in SLING-4318, about making the SLING-848 URIs > discoverable. >
Thanks for the suggestion, I'll move the versions to a new subtree so we can extend the JSON in the future. > About https://github.com/apache/sling/pull/57, the URI parameters, is > there an alternative that avoids modifying the ResourceProvider > interface? There's probably lots of ResourceProvider in the field, so > maybe creating a child ResourceProvider2 interface would be less > disruptive? > How about creating ParametrizableResourceProvider with the extended get() method? If there are some parameters and the ResourceProvider implements also PRP, the resource resolver will invoke the new get() method. Otherwise it'll stick to the old one. The PRP would be an extending interface (like AttributableResourceProvider), not a replacement for the RP. Regards, Tomek -- Tomek Rękawek Senior Software Engineer Cognifide Polska Sp. z o.o. skype: trekawek www.cognifide.com
