I am very pleased to announce that the first nine project proposals for the Eclipse Enterprise for Java (EE4J) top-level project have been formally published for community review. This is the first step to making the migration of Java EE to the Eclipse Foundation a reality.
The process of migrating the EclipseLink (JPA) and Eclipse Yasson (JSON-B) projects to EE4J is also underway.
We look forward to feedback from the community on these proposals!
EE4J Project Proposals
Name: Eclipse Grizzly
Top-Level Project: EE4J
Stage: Community Review
Project Link: https://projects.eclipse.org/proposals/eclipse-grizzly
Description: Writing scalable server applications in the Java
programming language has always been difficult. Before the advent of the Java New I/O API (NIO), thread management issues made it impossible for a server to scale to thousands of users. The Eclipse Grizzly NIO framework has been designed to help developers to take advantage of the Java NIO API.
Name: Eclipse OpenMQ
Top-Level Project: EE4J
Stage: Community Review
Project Link: https://projects.eclipse.org/proposals/eclipse-openmq
Description: Eclipse Open Message Queue (OpenMQ) is a complete message-oriented middleware platform, offering high quality, enterprise-ready messaging.
OpenMQ is included in GlassFish.
Name: Eclipse Mojarra
Top-Level Project: EE4J
Stage: Community Review
Project Link: https://projects.eclipse.org/proposals/eclipse-mojarra
Description: Eclipse Mojarra is the Reference Implementation for the JavaServer Faces specification (JSR-372). JavaServer Faces (JSF) is a Java specification for building component-based user interfaces for web applications. It is also a MVC web framework that simplifies construction of user interfaces (UI) for server-based applications by using reusable UI components in a page.
Mojarra is included in GlassFish.
Name: Eclipse Message Service API for Java (JSR-914)
Top-Level Project: EE4J
Stage: Community Review
Project Link: https://projects.eclipse.org/proposals/eclipse-message-service-api-java
Description: JSR- 914: The Java Message Service (JMS) API is a Java Message Oriented Middleware API for sending messages between two or more clients. It is an implementation to handle the Producer-consumer problem.
Name: Eclipse Tyrus
Top-Level Project: EE4J
Stage: Community Review
Project Link: https://projects.eclipse.org/proposals/eclipse-tyrus
Description: Eclipse Tyrus provides a reference implementation for Java API for WebSocket, starting from the specification defined by JSR-356.
Name: Eclipse Java API for RESTful Web Services (JAX-RS)
Top-Level Project: EE4J
Stage: Community Review
Project Link: https://projects.eclipse.org/proposals/eclipse-restful-web-services-api-java
Description: JAX-RS: Java API for RESTful Web Services (JAX-RS) is a Java programming language API spec that provides support in creating web services according to the Representational State Transfer (REST) architectural pattern.
Name: Eclipse Jersey
Top-Level Project: EE4J
Stage: Community Review
Project Link:https://projects.eclipse.org/proposals/eclipse-jersey
Description: Eclipse Jersey is a REST framework that provides JAX-RS (JSR-339) Reference 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.
Name: Eclipse WebSocket API for Java (JSR-356)
Top-Level Project: EE4J
Stage: Community Review
Project Link: https://projects.eclipse.org/proposals/eclipse-websocket-api-java
Description: Java API for WebSocket (JSR-356), specifies the API that Java developers can use when they want to integrate WebSockets into their applications – both on the server side as well as on the Java client side.
Name: Eclipse JSON Processing
Top-Level Project: EE4J
Stage: Community Review
Project Link: https://projects.eclipse.org/proposals/eclipse-json-processing
Description: Eclipse JSON Processing (JSON-P) is a Java API to process (e.g. parse, generate, transform and query) JSON documents. It produces and consumes JSON in a streaming fashion (similar to StAX API for XML) and allows to build a Java object model for JSON using API classes (similar to DOM API for XML).
