which filter is run first, lower or higher order/priority/ranking number?
you can specify the "ranking", "prioritisation" or "order" (called different things in different places) using this:
@ServiceRanking(-200)
The give the following situation:
600 : class com.day.cq.wcm.foundation.forms.impl.FormsHandlingServlet (id: 2255, property: service.ranking=600); called: 23; time: 97ms; time/call: 4217µs
0 : class com.adobe.aem.graphql.sites.ui.admin.impl.FeatureToggleFilter (id: 1373, property: none); called: 0; time: 122ms; time/call: -1µs
which is run first, the filter with 600, or the one with zero as the raking order?
so does
a) FormsHandlingServlet fitler call FeatureToggleFilter
or
b) FeatureToggleFilter call FormsHandlingServlet
The documentation says:
Filter ordering is defined by the filter.order property whose default value is Integer.MAX_VALUE where smaller values have higher priority over higher values.
This would imply b), but most people think its a).