Community
Participate
Working Groups
We should not weave for change tracking when any one mapping acccessor on a class uses VIRTUAL access (has a VirtualAttributeAccessor) Current testing model (using mock virtual classes) used in the extended jpa test suite: org.eclipse.persistence.testing.models.jpa.xml.advanced.Shovel* Explicit @ChangeTracking(DEFERRED) added to Shovel to ensure the testMockDynamicClassCRUD test from org.eclipse.persistence.testing.tests.jpa.xml.advanced.EntityMappingsAdvancedJUnitTestCase requires this to ensure the test passes (i.e. correctly detects an update)
We should still weave these classes. We have enough information to weave correctly we just need to add the support.
My hope is that VIRTUAL access becomes an additional means by which users can build extensible models. Currently they can add a element-collection to store additional values in a secondary table but adding VIRTUAL attributes with additional columns added to the table also is of interest to some. I'll build up an example and attach but I believe 2.2 is a reasonable plan for this assuming the bug gets some votes.
Hello, any progress here? By the way, this bug can be fixed just by calling "_persistence_propertyChange" method with corresponding params. Thanks Vlad
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink