Andi Huber created CAUSEWAY-3500:
------------------------------------
Summary: [Persistence] Cleanup ambiguous EntityState Terminolgy
Key: CAUSEWAY-3500
URL: https://issues.apache.org/jira/browse/CAUSEWAY-3500
Project: Causeway
Issue Type: Improvement
Components: Persistence JDO, Persistence JPA
Reporter: Andi Huber
Assignee: Andi Huber
Fix For: 2.0.0-RC2
In the framework's context DETACHED just means PERSISTABLE but currently
NOT-ATTACHED.
However, within JDO and JPA context, DETACHED means that an entity can be still
worked with then be made persistent again later, whilst the persistence layer
will have kept track of any changes in between.
While JDO supports this technology, we historically never enabled it. Instead
the framework relies on Bookmarks/OIDs to re-fetch entities, should there be an
interaction.
JDO instead offers the lightweight HOLLOW state for entities, which JPA does
not.
So my goal is to clean up the EntityState enum, perhaps rename some of the
states and correct any ambiguous associated java-doc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
