Creation Review

Type

Creation

State

Successful

End Date of the Review Period

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.

Monday, December 18, 2017 - 12:00

Project

Jakarta Messaging

Proposal

Eclipse Project for JMS

Monday, November 13, 2017 - 11:59 by Dmitry Kornilov

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.

Project

Jakarta Messaging

Parent Project

Eclipse EE4J

Proposal State

Created

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 Proeject for JMS provides the API and TCK for Java™ Message Service (JMS) API, starting from the specification defined by JSR-343.

An implementation for JMS is part of the Eclipse OpenMQ proposal.

Description

JSR- 343: The Java Message Service (JMS) API is a Java Message Oriented Middleware API for sending messages between two or more clients. It is a programming model to handle the producer-consumer messaging problem.

Licenses

Eclipse Public License 2.0

一 (Secondary) GNU General Public License, version 2 with the GNU Classpath Exception

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.

People

Project Leads

Committers