Explore >> Select a destination
|
You are here 
|
www.javaadvent.com | ||
| | | | |
benoitpasquier.com
|
|
| | | | | A recurring challenge in programming is accessing a shared resource concurrently. How to make sure the code doesn't behave differently when multiple thread or operations tries to access the same property. In short, how to protect from a race condition? | |
| | | | |
in.relation.to
|
|
| | | | | Jakarta Data is a new specification for persistence in Java, scheduled for release as part of the EE 11 platform. In a previous post I introduced the basic features of a Jakarta Data repository, with a strong emphasis on how Jakarta Data provides compile-time type safety, enabling static analysis performed by an annotation processor. This involved moving some information that used to be expressed in procedural code into: annotations like @Query and @Find, and the names and types of repository method parameters. Today we're going to talk about some more dynamic features of Jakarta Data. You might anticipate that these would come with a loss of type safety, but we've found a way to avoid that. The essential ingredient is a static metamodel. | |
| | | | |
thomascountz.com
|
|
| | | | | Personal site of Thomas Countz | |
| | | | |
nebulas.sfwa.org
|
|
| | | |||
