Why do you want something we already have? We have the startup support and you can simply register a listener doing the trick. That is in fact our ready service. Let's not overcomplicate this thing
Carsten 2014-07-23 15:12 GMT+02:00 Bertrand Delacretaz <[email protected]>: > On Wed, Jul 23, 2014 at 3:07 PM, David Bosschaert > <[email protected]> wrote: > > ...So, e.g.: > > -x "(objectClass=o.a.s.SlingReady)" > > or > > -x > > Where the latter uses a default filter... > > Sounds great to me! > > We already have something like that in > contrib/extensions/startup-filter and startup-filter-disabler, the > latter registers a StartupFilterDisabler service to remove the HTTP > 503 filter that the former registers at startup. > > What you suggest is more generic, I like it. We could then rewrite > those modules to use the SlingReady service. Which makes me think that > the default filter that you suggest should come from a framework > property. > > -Bertrand > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
