It’s first sources which are actually transferred from Oracle to Eclipse. First two projects (Yasson and EclipseLink) were already in Eclipse Foundation, but under different root project.
More project coming soon! The firsts make history. And the first one was JSON-P!
I am happy to announce that today EclipseLink and Yasson have been transferred under EE4J and officially became first two EE4J projects! EE4J now contains some real Java code and it’s a big step forward!
We are hiring experienced developers for working on Java EE / EE4J projects to my team in Prague. Reallocation is possible. To apply click here or contact me directly using Contact page on this web site.
I am happy to announce that we are planning to transfer Yasson and EclipseLink projects to EE4J. These will be one of the first projects transferred because they are a part of Eclipse Foundation already. I already posted announcement in EE4J community mailing list here:
The transfer will not affect any committer rights, but it may introduce some changes in web site URL, mailing lists, etc.
I’ll keep you updated about the progress.
JSON support is an important part of Java EE. This session provides a deep dive into JSON-P and JSON-B APIs, explains how they are connected and can be used together. I will introduce and demonstrate new JSON-P features such as JSON Patch, JSON Pointer, and JSON Merge Patch as well as JSON-B features such as default and customized mapping, adapters, and serializers.
I am glad to inform you JSON-B RI and EclipseLink projects have been successfully separated. It was not a union of heart, but more marriage of convenience. Both projects had the same committers. Therefore, JSON-B RI was started in a directory inside EclipseLink project. But when JSON-B RI project started to be more and more mature we started to realize that the idea of hosting it inside EclipseLink project was not so good. These projects have different release cycles and different committers. Currently all JSON-B RI committers are EclipseLink committers, but not vice versa. Also, it can change in future, when more JSONB-RI committers are added.
Here are slides from my sessions on java2days conference in Sofia (Bulgaria) which I’ve done together with Werner Keil. I would like to say thanks to all people who attended my talks. Your questions were smart and your ideas were constructive.
Slides from my presentation on GeeCon 2016 on 20 October 2016. I am talking about the changes in Java EE platform addressing trends in the industry towards Cloud and Microservices. I am explaining how this changes applied to the Java EE 8 scope and what is planned for the next Java EE 9 release.
This is an official recording of my JavaOne 2016 session “Configuration for Java EE and the Cloud” from 21 September 2016.
In the modern world, where applications consist of microservices and are deployed in a cloud, developers are facing many issues related to apps config. How to deploy an app in different environments without cracking its package. How to apply configuration for deployed instances of an app without redeployment. How an app can be notified if some configuration properties changes. This session introduces a standardization effort tasked with solving these problems by defining a Java EE config service. Such a service is aimed at the cloud and provides the ability to create one or more configurations that are independent of and decoupled from apps using them. The session describes how such a service fits into the Java EE family and integrates with other Java EE frameworks.