Deprecating JPA no-args constructors

1. persistence

   1 2 225 7.6 Java

   

   You can open issues related to the API here: https://github.com/eclipse-ee4j/jpa-api/issues

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. amber-docs

   2 58 145 4.2 HTML

   https://openjdk.org/projects/amber

   

   [1] https://github.com/openjdk/amber-docs/blob/master/eg-drafts/reconstruction-records-and-classes.md

4. jmolecules

   3 4 1,347 6.7 Java

   Libraries to help developers express architectural abstractions in Java code

   

   You could move towards modeling your code around DDD building blocks (like aggregates etc.) and declare those concepts in code explicitly using jMolecules types. There is a dedicated jMolecules Integrations ByteBuddy Plugin, that would then add the necessary boilerplate code and default mappings required by the expressed concept. This makes the code shown here a fully working JPA model. You can argue that the lack of JPA oddities is odd itself in the first place but I like the idea of expressing the architectural concept explicitly and the technology integration completely flowing from that.

Suggest a related project