Eclipse Jersey

Basics

This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process) and is written to declare its intent and scope. We solicit additional participation and input from the community. Please login and add your feedback in the comments section.

Parent Project:

Eclipse EE4J

Background:

This project is created as part of the process of transitioning Oracle Java EE 8 and GlassFish technologies to the Eclipse Foundation as described in The Eclipse Enterprise for Java Project Top Level Project Charter (https://projects.eclipse.org/projects/ee4j/charter).

Scope:

Eclipse Jersey provides an implementation for Java API for RESTful Web Services (JAX-RS), starting from the specification defined by JSR-370.

The JAX-RS API and TCK are being proposed as part of the Eclipse Project for JAX-RS project.

Description:

Eclipse Jersey is a REST framework that provides a JAX-RS (JSR-370) implementation and more. Jersey provides its own APIs that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development. Jersey also exposes numerous extension SPIs so that developers may extend Jersey to best suit their needs.

Goals of Jersey project can be summarized in the following points:

Track the JAX-RS API and provide regular releases of production quality implementations that ships with GlassFish;
Provide APIs to extend Jersey & Build a community of users and developers; and finally
Make it easy to build RESTful Web services utilising Java and the Java Virtual Machine.

Why Here?:

The top level EE4J project was created consistent with the direction described in The Eclipse Enterprise for Java Project Top Level Project Charter (https://projects.eclipse.org/projects/ee4j/charter). This project is created under the top level EE4J project as one of Oracle Java EE 8 and GlassFish technologies being transitioned to the Eclipse Foundation.