GlassFish - World's first Java EE 7 Application Server


Jersey GFv3 Integration QE One Pager

[

Unknown macro: {TableOfContents title=' '}

|(TableOfContentstitle='')]

1. Introduction

1.1. Project/Component Working Name:

Jersey

1.2. Name(s) and e-mail address of Document Author(s)/Supplier:

Naresh: Srinivas.Bhimisetty@Sun.COM

1.3. Date of This Document:

02/26/08

2. Technical Description:

2.1. Details:

So far, Jersey has been integrated and available at GFv3 Prelude as an update center module.
The module adds 4 osgi modules into GlassFish glassfish/modules subdirectory:

  • jsr-311.jar (JAX-RS API)
  • jersey-bundle.jar (Jersey module)
  • asm.jar (osgified 3rd party lib)
  • jettison.jar (osgified 3rd party lib)

Additionaly, the package also includes a jersey subdirectory with JAX-RS and Jersey javadocs and example applications.

Engineering one pager is at http://wiki.glassfish.java.net/Wiki.jsp?page=JerseyV3OnePager

2.2. In Scope:

Integration of Jersey related libraries, so that end users can deploy
Jersey based web applications to GlassFish without a need to bundle Jersey
specific libraries along with the application war files. This covers also integration of javadocs and example apps.

2.2. Out of Scope:

The project does not cover integration into GlassFish admin console neither any special asadmin commands.

2.3. Test Cases

S.No. Test Description
1 Verify that when Jersey is installed using UC, the glassfish/modules has the jar files jsr-311.jar, jersey-bundle.jar, asm.jar and jettison.jar
2 Verify that a directory named jersey is created under the v3-prelude installation when Jersey is installed through the UC
3 Verify that the 'license' and 'readme' files are created under 'jersey'.
4 Verify that the jersey directory has subdirectories 'apidocs' and 'samples'. The apidocs should have the javadoc for jersey and jsr-311.All the samples mentioned in the README.html should be present in the 'samples' directory and vice-versa.
5 Verify that for each sample in the samples directory, the pom.xml has the scope attribute set to 'provided' for the dependencies on jersey-server, jersey-client, jersey-bundle, jsr-311, asm and jettison.
6 Verify that when the samples are packaged using 'mvn clean package', the bundled war file doesn't have any of the jersey jars in it. The war should not have asm.jar or jettison.jar too.
7 Verify that the war file bundled above could be deployed on the GlassFish instance.

%%

2.4. Automation Plan

It is planned to automate the whole process of downloading the GlassFish build, installing the Jersey module using the UC module, and testing the cases mentioned above. A Hudson job would be created which would take care of all this.

3. Reference Documents:

Jersey specific documents should be accessible via Jersey project web page

4. Schedule:

4.1. Projected Availability:

May 2009