JerseyAutoConfiguration:requestContextFilter struggles with WebMvcAutoConfiguration:requestContextFilter

[cpiepel]

As described in #15048, the requestContextFilter bean from JerseyAutoConfiguration struggles with the request ContextFilter bean from WebMvcAutoConfiguration. @wilkinsona was going to remove Jersey's RequestContextFilter.

Maybe due to the restore of JerseyAutoConfiguration, requestContextFilter from JerseyAutoConfiguration was also restored.

Can you please check this.

[wilkinsona]

The auto-configuration of a requestContextFilter bean was reinstated in 2.1.3 as its removal caused a regression. Its presence in 3.x is intentional.

In what way is there a struggle here? When both Spring MVC and Jersey are being used, you should end up with a single RequestContextFilter bean. As described in #15376, there are also application properties that can be used to fine-tune the filter's ordering.

If you would like us to spend some more time investigating, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[spring-projects-issues]

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.