Hi Bertrand, FWIW, I was thinking about something very similar (although I was thinking of calling it 'scope', not 'usage'), but never got around to implementing it.
+1 for me. Justin On Tue, Aug 6, 2013 at 10:58 AM, Bertrand Delacretaz <bdelacre...@apache.org > wrote: > Hi, > > I'd like to use BindingsValuesProvider services in my health check > module, to provide bindings like "jmx" for scripted health checks, > which should be ignored for general Sling scripting (or not - some > providers might apply to both general scripting and health checks). > > I'm thinking of adding an optional "usage" service property to > BindingsValuesProvider services, does anyone see a problem with that? > > The Sling script engine would then consider only > BindingsValuesProvider which have no usage property (for backwards > compatibility) or which have usage=scripting. > > And my health checks would consider only BindingsValuesProvider which > have usage=healthcheck. > > -Bertrand >