Hmm, this doesn't really convince me. So this means there is no way to set the context apart from creating/retrieving a script engine by hand (java code)? So scripts run with the usual Sling script resolution will always just use BVPs not marked for any context and BVPs marked for the context request. I still fail to see the usefulness - but as you all seem to go crazy about it, I wont block this
Carsten 2013/8/7 Bertrand Delacretaz <[email protected]> > On Wed, Aug 7, 2013 at 10:26 AM, Carsten Ziegeler <[email protected]> > wrote: > > Again, I'm still missing a suggestion on how to mark a script to run in a > > given context... > > You don't. > > There are request processing scripts, the ones we have and always had > - there's no change for those, except that with this change they won't > get any BVPs which are marked for a context that is not "request". > Existing BVPs are not marked like that so no change. There's no way > and no need to mark those scripts for a different context, they are > "request" processing scripts. > > Then there are new health check (mini-)scripts which are different > animals: they are provided in OSGi configs as shown earlier in this > thread. Their context is hardcoded to "healthcheck", there's no need > to change that. > > Another way to look at this, and maybe I should have phrased my > proposal like that, is that the goal is to setup different script > engines: currently we're just using a "request processing" script > engine, I need a "healtcheck" script engine with different bindings, > and it makes sense to generalize the idea. > > -Bertrand > -- Carsten Ziegeler [email protected]
