我正在使用DynamicFeature
in Jersey https://jersey.java.net/documentation/latest/filters-and-interceptors.html#d0e10049将容器请求过滤器动态绑定到某些特定的资源方法。除了DynamicFeature
,我还有适用于所有资源方法的常规过滤器。但是,我发现这些过滤器的优先级/顺序没有按预期工作。例如:
public class MyDynamicFeature implements DynamicFeature {
@Override
public void configure(ResourceInfo resourceInfo, FeatureContext featureContext) {
featureContext.register(MyDynamicFilter.class, 2);
}
}
public class MyDynamicFilter implements ContainerRequestFilter {
@Override
public void filter(ContainerRequestContext containerRequestContext) throws IOException {
System.out.println("Hey! I am dynamic!");
}
}
public class MyStaticFilter implements ContainerRequestFilter {
@Override
public void filter(ContainerRequestContext containerRequestContext) throws IOException {
System.out.println("Hey! I am static!");
}
}
In the ResourceConfig
,我注册了DynamicFeature
和具有优先级的过滤器:
register(MyDynamicFeature.class, 1);
register(MyStaticFilter.class, 3);
理想情况下,如果请求通过过滤器,我希望从日志中看到:
Hey! I am dynamic!
Hey! I am static!
因为动态过滤器比静态过滤器具有更高的优先级,但相反,我看到
Hey! I am static!
Hey! I am dynamic!
所以看起来动态绑定的过滤器总是出现在静态绑定的过滤器之后。为什么它不尊重我设定的优先事项?