It has been a long time i posted anything about the Jersey project here.
As Paul has left Oracle, and i am taking over his leadership role for Jersey 1.x, i think it is the right time to start blogging again.
This post should give you an overview of what are the plans for the Jersey 1.x in the near future.
We want to improve Jersey integration with both GlassFish and WebLogic application servers,
with focus on the following areas:
Another important thing we want to work on is non-blocking asynchronous web client, including
support for WebSocket and HttpStreaming. For the client generally, we want to look
at the possibilities to get them automatically generated from WADL, which probably
includes also some WADL related work on the server side (XSD inclusion).
Besides the areas mentioned above, we will also be continuing on bug fixing and working with the community
on any other stuff. Jersey 1.x might still be a playground for emerging JAX-RS 2.0 features.
Another, often underestimated thing, is the project infrastructure. We are willing
to continue improving it. Pavel recently added Maven 3 support, and Jersey now builds faster.
Last but not least, we would like to get back to the 6-8 week release cycle. The next, 1.6 version, release is planned for the end of this week.