Hi Jörg,
there is the option "autoDisableFilter" [1] in the
ServiceUnavailableFilter - if true the filter automatically unregisters
itself upon first non-503 result. Once unregistered it listens to
FrameworkEvent.STARTLEVEL_CHANGED events to reregister once needed (the
shutdown case). During
Hi Georg,
Merging the 2 implementations oas-startupfilter + -disabler and
oas-starter-startup makes fully sense to me, although I am bit hesitant by
replacing the basic approach.
these 2 have a rather static assumption, when the application is up, and
their sole purpose is to indicate that. And
