Fix memory leak (#6075) * Fix memory leak beanManager was set to threadLocal from a configurator that was post-init after the ComponentProvider configurator which is supposed to free the thread local. The beanManager thread local was never removed afterwards. I switched the order of calling post-init so that configurators go in reversed order compared to calling init * Fix memory leak - fix failing tests Revert the change to run postInit on all configurators in reversed order. Instead run postInit only on the specific Component configurator last, while initialize runs in the original order. This cleans up thread locals safely, without changing the order of other configurators, which was breking other functionality.
Jersey is a REST framework that provides JAX-RS Reference Implementation and more. Jersey provides its own APIs that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development. Jersey also exposes numerous extension SPIs so that developers may extend Jersey to best suit their needs.
Goals of Jersey project can be summarized in the following points:
Jersey is licensed under a dual license - EPL 2.0 and GPL 2.0 with Class-path Exception. That means you can choose which one of the two suits your needs better and use it under those terms.
We use contribution policy, which means we can only accept contributions under the terms of ECA.
See the Jersey website to access Jersey documentation. If you run into any issues or have questions, ask at jersey-dev@eclipse.org (need to subscribe first), StackOverflow or file an issue on Jersey GitHub Project. You can follow us on Twitter, too.