A bit of advise from someone that has worked in Java EE expert groups for a while - take it for what it is worth.
A more detailed code example illustrating the idea really helps as well as showing some evidence that you have researched what is available today. For example, have you looked into things like Hibernate Envers? For some of your other suggestions, have you done enough research on what is already available with Java EE 8 security? Why not add a code example showing what is available today and what you would like to see instead?
In general, these email aliases are not the best place for very preliminary brainstorming. Most people here are far too busy for that. For very preliminary ideas, I suggest a place like Code Ranch. There are plenty of people there that know Java EE well and have a bit more of a learning orientation and can help you flush the basics out. Once that is done, you could always post here if it is still necessary.
Hope it helps.
Cheers,
Reza Rahman
Principal Program Manager
Java on Azure
Please note views expressed here are my own, not necessarily that of my employer.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
Date: 5/29/19 5:53 AM (GMT-05:00)
Subject: [jakarta.ee-community] JPA Versioning for data
Hi all!
I hope it is not an off topic, I think the version handling (not concurrency) of entity would be useful. I mean, when some one update an entity then the copy of old version will be added in other table.
Best regards/Üdvözlettel,
Gergely Molnár
