Tuesday Jun 28, 2011

Jersey 1.8 is released

On the last Friday, we have released the 1.8 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 here.

This, 1.8, version of Jersey is going to be integrated into GlassFish 3.1.1 and contains bug fixes mainly. The most important fix from this perspective is included in the JAX-RS/EJB integration layer. It is now possible to implement JAX-RS resources as EJB Session beans, which implement local and/or remote interfaces. This functionality was broken in previous releases.

Another great addition should come into the client space, where Pavel has already done some preparation in the client API (including some breaking changes there) for the non-blocking asynchronous client feature. The implementation is already part of the experimental Jersey space and should be included as part of the stable Jersey bits in some of the coming releases.

For feedback send email to:

users@jersey.java.net (archived here)

or log bugs/features here.

Thursday Apr 14, 2011

JAX-RS Presentation at JavaOne in Moscow

I have just finished my JAX-RS presentation at JavaOne in Moscow. In fact, I have pretty much re-used what Paul and Roberto were presenting in San Francisco. Only dropped the EJB/CDI integration part to fit into the 45 minute time slot.

slides

demos

Monday Mar 28, 2011

Jersey 1.6 is released

On the last Friday, we have released the 1.6 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 here.

In this release, we started with the jersey-server modularization. Only recently, Grizzly version 2.0 was released. We moved the Grizzly 2 Jersey module from the experimental area, added the Grizzly HTTP Servlet support and some tests, and created a new Jersey jersey-grizzly2 module. At the same time we extracted the Grizzly version 1 support from the jersey-server module, and introduced a new, jersey-grizzly module. We also switched the majority of the Jersey functional tests from Grizzly 1 to Grizzly 2 to make sure everything works fine there. Grizzly 2 support was added to the Jersey test framework as well.

Besides the Grizzly 2 integration, Pavel spent some cycles on the test code coverage report for Jersey.

Another update in the Jersey 1.6 release is a great improvement of the Jersey OAuth client provided by Martin. To depict the functionality Martin also introduced a new, Jersey OAuth Twitter Client example.

For feedback send email to:

users@jersey.java.net (archived here)

or log bugs/features here.

Tuesday Mar 22, 2011

Jersey 1.x Plans

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:

  • Multiple Jersey versions running simultaneously within one container
  • EJB integration
  • Monitoring
  • Client injection

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.

Saturday Oct 17, 2009

Přednáška o JAX-RS a Jersey na WebExpo konferenci

WebExpo je údajně největší česká konference zaměřená na web. Za chvíli tam mám prezentovat JAX-RS a potažmo Jersey a už se moc těším. Je to vlastně poprvé, kdy budu prezentovat mimo Java komunitu, a moc mě zajímá, jak na to budou lidi reagovat. Taky jsem zvědavý na přednášky ostatních.

Věším slajdy na http://blogs.sun.com/japod/resource/Jersey-WebExpo-Praha.pdf a vrhám se do víru konference...

WebExpo 2009

Monday Apr 27, 2009

Jersey 1.0.3 GlassFish V3 packages split up

Jersey version 1.0.3 is now available also to GlassFish V3 Prelude users via GFv3 update center. I am writing this, because several changes happened about how things work there.

As you can see at the snapshot, the first big change relates to number of Jersey packages. Started from the 1.0.3 version, we are providing two separate packages.

We are going to integrate with GlassFish V3 bits, so that people would not need to install Jersey separately. And as we wanted to lower the Jersey footprint in GlassFish V3, we have broken the original Jersey package down into two separate modules:

  • Jersey Core
  • Jersey Examples and Documentation

The "Jersey Core" package contains OSGI modules for jersey-bundle, jettison, and jackson-asl libraries. This should be sufficient for you to deploy Jersey based web applications to GlassFish V3 Prelude without a need to bundle any Jersey related jars with your application WAR file and should be good for production.

"Jersey Examples and Documentation" package contains Jersey API javadocs and some examples. This package should be useful especially for developers, who want to learn Jersey, and see how it works before developing their own RESTful web applications. If you choose this package, the UC client will automatically install also the "Jersey core" module, and you will get installed everything you need to start up.

A rather cosmetic change happened to location, where jersey subdirectory gets installed into. It has moved from $AS_HOME/jersey to $AS_HOME/glassfish/jersey.

When upgrading from earlier versions of Jersey, you could be a bit confused with consequences of the above described changes. So if you upgraded into a newer Jersey version and try to figure out, where all Jersey examples and docs went, just install "Jersey Examples and Documentation" in addition and it should re-appear in $AS_HOME/glassfish/jersey.

About

Jakub Podlesak-Oracle

Search

Archives
« April 2015
SunMonTueWedThuFriSat
   
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
  
       
Today