Data-centric libraries often need to access private state of classes provided by the library user.
An example is Hibernate ORM.
When the @Id annotation is given on a field of an entity, Hibernate will by default directly access fields - as opposed to calling property getters and setters - to read and write the entity’s state.
Usually, such fields are private.
Accessing them from outside code has never been a problem, though.
The Java reflection API allows to make private members accessible and access them subsequently from other classes.
With the advent of the module system in Java 9, rules for this will change a bit, though.
In the following we’ll explore the options authors of a library provided as a Java 9 module have to access private state of classes defined in other modules.
WildFly, as a compatible Java EE 7 implementation, comes with Bean Validation 1.1 and its reference implementation Hibernate Validator 5 out of the box.
In the following we’ll show you how easy it is to upgrade the server’s modules to the latest Bean Validation release, using a patch file provided by Hibernate Validator.
I’m honoured to confirm that I’ll be at Devoxx UK this May in London.
Come along in Gallery Hall at 12:55 on Thursday 11th of May to see a quick
demo of Hibernate OGM used to migrate a JPA application from using a relational
database to using a fast, scalable and highly available in memory data grid.
Red Hat has been exploring serverless (aka FaaS) through the Fabric8 Funktion project.
It has been long due for us to get serious on the subject.
We are turning all of our libraries into services starting today.
This is going to be a multi year effort but we are committed to it.
We thought hard and long about which service to start with.
In our performance lab, we realized that the slowest and most expensive part of serverless functions was CPU branch misprediction.
In a serverless approach, you want to squeeze as much operations per CPU cycle as possible.
Any misprediction has huge consequences and kill any of the mechanical sympathy effort we put in libraries like vert.x.
In our experiments, we found that the optimal solution was to get rid of if branches in serverless functions.
We are proud to introduce IF as a Service or IFaaS (pronounced aye face).
Your code changes from: