Support private persistent attributes in @MappedSuperclas
Description
Attachments
3
is a fix for
is duplicated by
Activity
Show:
Former user March 15, 2017 at 12:21 AM
Fixed in 5.1 branch as well.
Craig Andrews November 29, 2016 at 9:37 PM
is not for @MappedSuperclass but it sounds like it may be related or potentially the same cause.
Luis Barreiro September 19, 2016 at 12:23 PM
the open PR addresses all the concerns raised on this issue.
Former user September 17, 2016 at 12:05 AM
, is there something more to address related to 's comment above?
Alexander Pinske August 5, 2016 at 2:48 PM
I don't see how the resolves the issue. I don't have any time to test it, unfortunately. That still leaves the problem that a mapped superclass is not enhanced, when there multiple mapped superclasses in the inheritance chain.
I pushed the use of byte code enhancement into the future, as is its not mature enough yet.
Thanks for your efforts. Best regards!
When bytecode enhancement is enabled a change to a property in a mapped superclass does not mark the entity dirty. Subsequently that change is not persisted.
Find attached a test case. Run with "mvn test". The change to setParentValue() does not get applied on flush. When enhancement is turned off, the test case works as expected.
The generated methods in the mapped superclass do not delegate to any dirty tracker.
I would expect that e.g. the entity overrides the superclass methods and in there delegates to its dirty tracker.