tree 2549a4f5dcff12a351e245e25e6bbf3212a36875
parent 136ff59cad9d06376a7610a15c2a4003a304e855
author abcpro1 <abcpro11051@disroot.org> 1667845852 +0000
committer abcpro1 <abcpro11051@disroot.org> 1668030540 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iHUEABYKAB0WIQQSQVc4fwEiTkR4o0LP8sylYYU0oAUCY2wgTAAKCRDP8sylYYU0
 oFpUAP4lvSz0vCk2JO+BvEUmyNwb2PXHCJbNawiL+ePdg0NsPgEAi3RU4R+1hg8w
 WhMa3yQtZa/mPJyvcfnXbwitUZ0Niw0=
 =/XRU
 -----END PGP SIGNATURE-----

Jersey 2: Create a custom annotation to register resource filters

There is no direct equivalent of the @ResourceFilters annotation in Jersey 2.
The best alternative to define a custom annotation and use a DynamicFeature provider
to interpret this annotation and register filters.

Why not define a annotation for each filter and use Jersey's @NameBinding mechanism?
@ResourceFilters works differently than @NameBinding. A @ResourceFilters annotation
on method overrides the class level annotation; In this case, all filters
defined on the class level are discarded. This behaviour can't be achieved
with @NameBinding.

References:
https://eclipse-ee4j.github.io/jersey.github.io/documentation/2.37/filters-and-interceptors.html#d0e10127
https://jakartaee.github.io/rest/apidocs/2.1.6/javax/ws/rs/container/DynamicFeature.html