Yasson 1.0.1 is released

dmitrykornilov ,

I am pleased to inform you that a new version of Yasson (1.0.1) has been released today.

Bugs fixed:

  • FIXED: [#57] Unexpected behaviour from @jsonbtypeadapter when marking a field bug
  • FIXED: [#48] Serializing ‘naked’ enum throws exception java.lang.IllegalAccessException bug
  • FIXED: [#47] Serialising enum uses toString() method not name() as specified in section 3.9 of specification bug
  • FIXED: [#43] Date format customisation is ignored if custom instantiation is used bug
  • FIXED: [#42] Serializing a map doesn’t use serializers bug
  • FIXED: [#39] Nillable customizations ignore default rules for processing classes bug
  • FIXED: [#34] NullPointerException when @jsonbtransient is applied on property without setter bug

Other

  • Switched to JSON-P 1.1.2
  • Performance improved

The release is available on Maven Central.

Yasson and EclipseLink go to EE4J

dmitrykornilov , ,

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:

https://dev.eclipse.org/mhonarc/lists/ee4j-community/msg00341.html

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.

Introducing Yasson

dmitrykornilov ,

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.

Continue reading →

Java2days 2016

dmitrykornilov , ,

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.

As bonus here is a link to a small photo album with night pictures of Sofia I took during my stay there.

Configuration for Java EE and the Cloud

dmitrykornilov ,

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.

Slides can be downloaded here.

Where do you want to go today?

dmitrykornilov

JavaOne is starting in two weeks. It’s time to take a look at the sessions and choose what to attend. There are many interesting sessions and sometimes some of them are at the same time. I’ve already made my list and decided to share it with you. The main interesting points for me are Java 9 and JavaEE.Next related topics. The list is sorted chronologically and includes sessions abstracts, date, place and my comments. Continue reading →