Deprecating JPA no-args constructors

• persistence

  2 177 9.0 Java
  

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

• amber-docs

  58 142 5.1 HTML

  https://openjdk.org/projects/amber

  

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

• WorkOS

  workos.com featured

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• jmolecules

  4 1,091 5.6 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