Eclipse Yasson and EclipseLink officially become first two EE4J projects

Dmitry Kornilov, EclipseLink and Eclipse Yasson lead announced in a recent blog post that both projects “have been transferred under EE4J and officially became first two EE4J projects.”

First two @EclipseEE4J projects! https://t.co/AFlVTXi3uF

— Dmitry Kornilov (@m0mus) December 19, 2017

EclipseLink Project

The EclipseLink project’s goal is to provide a complete persistence solution that is both comprehensive and universal. It will run in any Java environment and read and write objects to virtually any type of data source, including relational databases, XML, or EIS systems. EclipseLink will focus on providing leading edge support, including advanced feature extensions, for the dominant persistence standards for each target data source; Java Persistence API (JPA) for relational databases, Java API for XML Binding (JAXB) for XML, Java Connector Architecture (JCA) for EIS and other types of legacy systems, and Service Data Objects (SDO).

Find out more about it here. 

Eclipse Yasson

Eclipse Yasson is a Java framework which provides a standard binding layer between Java classes and JSON documents. This is similar to what JAXB is doing in the XML world. Yasson is an official reference implementation of JSON Binding (JSR-367).

Find out more about it here. 

SEE ALSO: EE4J update: 9 new project proposals at the Eclipse Foundation

New EE4J project: Eclipse Ozark

The first step is the hardest, it seems. Now that there are two official projects under EE4J’s belt, it’s time to welcome more projects into the “family”.

Eclipse Ozark is the newest addition  — it’s “an implementation of action-based MVC specifiec by MVC 1.0 (JSR-371). It builds on top of JAX-RS and currently contains support for RESTEasy, Jersey and CXF with a well-defined SPI for other implementations”

New project: Eclipse Ozark falls under our @EclipseEE4J Top-level project! #EclipseOzark provides an implementation for Model View Controller API. https://t.co/Nsw1fVkLFU pic.twitter.com/0CPzaP3VUU

— Eclipse Foundation (@EclipseFdn) December 19, 2017

Why put it under EE4J? “This project is created under the top level EE4J project as one of technologies originally targeted for Java EE 8. It makes sense to follow the other technologies transfered by Oracle.”

Read more about Eclipse Ozark here.