I am changing the subject line and expanding the audience. I hope that is OK.
There are a number of specifications that should do due diligence with regards to alignment with Records in detail such as: JSON Binding, XML Binding, Persistence, Faces, Bean Validation and CDI.
Otherwise, someone should undertake the effort to write a series of tests to ensure things work correctly with scenarios involving these APIs and even perhaps throughout others too such as Jakarta REST and Messaging. This has been in my to-do list but frankly my bandwidth is not infinite for a middle aged developer with a demanding day job and a family. Some help would be most welcome.
Here is some preliminary analysis and discussion for Persistence:
https://github.com/kalgon/jpa-records/issues/1. The gist is that I don’t think Persistence needs to do anything right now, but there may be value in looking into a standard utility that can convert to and from Records.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
So, I'm kind of interested in turning this discussion around a little.
Given:
- You can develop your application with Java 17
- You can deploy your application to a Jakarta EE implementation that is certified and runs on Java 17
- This means that your application can use all Java 17 features you want, compile, and run on Java 17
What Java 17 features would improve the Jakarta EE APIs, and which specification does it make sense to add them?
Here's one example: Full support for Records in Jakarta JSON Binding
Today, you can simulate the Java Bean pattern by prefixing the field names with "get", but this is kind of an annoying workaround:
public record Greeting(String getName, String getMessage) {} is serialized to { "name": "", "message": "" }
Anything else?
Ivar