Do you or anyone else want to work with me on an analysis from the end user standpoint?
I don't think this is that straightforward and will require some level of scenario outlining. In particular, it is still unclear to me how Java Records fit into an overall application domain model vis-a-vis JPA entities and embeddables. It is possible the only use case for Java Records are as DTOs, in which case a possible set of enhancements could be just some relatively simple converters. There may even be space here for a vendor neutral small utility library and nothing in JPA itself (maybe part of DeltaSpike).
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.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message -------- From: kalgon@xxxxxxxxxxx Date: 4/24/20 1:29 AM (GMT-05:00) To: jpa developer discussions <jpa-dev@xxxxxxxxxxx> Subject: Re: [jpa-dev] Java Records Alignment?
Hi,
Aren't single-valued records somehow already supported by writing custom AttributeConverters?
For multi-valued records, a enhancement proposal for AttributeConverters exists:
|