Marek,
thank you for keeping us updated.
Do I understand correctly that the JAX-RS 2.1 RI is “Jersey 3.0” (not “Jersey 2.1”)?
Thanks
-Markus
Von: Marek Potociar [mailto:marek.potociar_at_oracle.com]
Gesendet: Montag, 13. April 2015 15:24
An: users
Betreff: [Jersey] What's up with Jersey these days?
To all Jersey users,
I’d like to share with all of you some details about what to expect from Jersey project in the next few months.
First of all, some Jersey 2.x news. Jersey 2.x development is now moving to a stabilization phase. For the next few months, the core Jersey team will once again need to switch gears and focus more on the development tasks for the products that pay our bills. Since Jersey is an important part of Oracle FMW products, we will also look into fixing the most pressing issues in the core Jersey modules to bring it to the best possible shape for future Oracle product releases. We will stop introducing new features (with perhaps 1-2 exceptions related to API refactoring) into Jersey 2.x code line. Also, the externally visible development activity may temporarily falter in this “stabilization” period as we dedicate part of our development focus to closed-source projects. For the next few months, we will stop following the regular 4-week release cycles. Again, this state is only temporary. We plan to resume the full-speed open-source development along with regular Jersey 2.x.x bug-fix release updates later in the summer this year. Jersey remains a healthy and fully supported project.
Now some thoughts on the planned Jersey.next development. As you are probably aware of by now, the JAX-RS.next (JSR-370)<
https://jcp.org/en/jsr/detail?id=370> JCP expert group work has already kicked-off and has slowly started to move towards it’s goal to produce a next revision of JAX-RS specification. For Jersey project that delivers reference implementation for JAX-RS, this means that we’ll start working on first builds of Jersey 3.x soon. Jersey 3.x will also become our next main Jersey release train as well as the main new-feature development focus theme in the next few years. We will start working on the first builds of Jersey 3.x as we’re back from our internal Oracle project duties. Unlike in Jersey 2.x that came with a complete code rewrite, we expect Jersey 3.x to be a much more evolutionary change, so most of your code that today leverages Jersey 2.x APIs should still work once Jersey 3.0 is released along with the release of the next version of JAX-RS specification. It is though clear already, that you will be required to upgrade to at least Java SE 8 to run Jersey 3.x runtime. This is currently the only known & planned upgrade limitation for the future Jersey & JAX-RS release.
Should you have any additional questions on the above, please do not hesitate to let us know. We will do our best to answer all your questions; though, obviously, we will not comment on any questions related to new Oracle product features and/or release dates.
May the REST be with you,
Marek Potociar
Safe Harbor Statement:
The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.