Recent Posts by Jakub Podlesak

While fixing a memory leak issue in JerseyClient some time ago i realised how easy it is to misuse the thing. In this blog post, i would like to introduce some tips to avoid unnecessary memory allocation and also to save some CPU cycles to achieve better throughput. Tip 1: Be careful when updating WebTarget config! In Jersey 1.x it was suggested to reuse Client instances (see here for details).In Jersey 2, reusing Client instances is still recommended, but as such it is not...

In my earlier post i described what we did in Jersey version 2.16 in order to make Jersey client work on Android. The whole idea was that after separating JAXB providers out from the Jersey core module, things would just work out of the box. Unfortunately, it turned out the JAXB provider separation was not enough. Basic things worked (see my original post for a test case application), but Jersey was still trying to pull in some types not available in Android environment....

We have just released the 2.17 version of Jersey, the open source, production quality, reference implementation of JAX-RS 2.0. To download Jersey 2.17, please check out our download page. You can also check out the refreshed Jersey 2.17 documentation: API: https://jersey.java.net/apidocs/2.17/jersey/ User Guide: https://jersey.java.net/documentation/2.17/ This version includes mainly bug fixes. Following is a list of the most important updates: Ability to use multiple Jersey based...

The short answer is: never!. I have seen several nasty (so called) "bugs" caused by this feature so that i felt like sharing this little advice via blog post: Never ever use JAX-RS class-path scanning feature in a production environment Class-path scanning looks like a handy feature. Let say you do not want bother with enumerating all the components you would like to include in your JAX-RS application. Then your JAX-RS application class could look like: import...

Introduction At the time of this writing, Java SE support is being discussed as one of important additions to CDI 2.0 specification. Existing CDI implementations brought this feature already, only container bootstrapping has not yet been standardized. In Jersey version 2.15 we introduced Weld SE support, so that people could take advantage of CDI features also when running in Java SE environment. As part of this work, the old Jersey CDI module has been refactoredso that it...

During my sabbatical week in January i have done some performance improvements in Jersey server core module. These changes are already included in Jersey version 2.16. To make sure the changes indeed made a positive difference i have re-established continuous performance testing for Jersey server side processing. These automated tests allowed Michal Gajdoš to collect some numbers that show how performance evolved within Jersey 2.x version space.In this post i would like to...

From time to time, people are asking for Jersey Client support on Android device. Until Jersey version 2.15 it was not possible to get Jersey client running on Android devices due to javax.xml.stream dependencies included directly in the Jersey client core module. A list of Android supported Java packages is available here and the javax.xml.stream package is missing there. Current Jersey snapshot version introduces a new JAX-B module, so that all JAXB-B Jersey client...

The latest promoted build of GlassFish 4.0 (glassfish-4.0-b43.zip) now contains upgraded Jersey version, 2.0-m05. Users are getting an early access to the implementation of some parts of the JAX-RS 2.0 API Early Draft Review 3. The appropriate JAX-RS bundle, version 2.0-m09 , gets bundled into GlassFish 4.0 as well. What should work The simple answer is: all the basic stuff. We have particularly tested the following two examples: simple hello world webapp multipart webapp Both...

We have just released the 1.12 version of Jersey, the open source, production quality, reference implementation of JAX-RS. The JAX-RS 1.1 specification is available at the JCP web site and also available in non-normative HTML here. For an overview of JAX-RS features read the Jersey user guide. To get started with Jersey read the getting started section of that guide. To understand more about what Jersey depends on read the dependencies section of that guide. See change log...