In the first implementation of the Retention Module the entity MemberProperties contains Views (private final List<String> viewReferences;). However, it would be better to save these separately. Current implementation works, but is awkward, since there's a method void saveMemberPropertiesWithoutViews(MemberProperties memberProperties); which saves the MemberProperties, but not the viewReferences. This is needed since viewReferences are updated based on other events (and it's not guaranteed that they are later in time than the creation of MemberProperties). Hence, the need for a split :-)
In the first implementation of the Retention Module the entity
MemberProperties
contains Views (private final List<String> viewReferences;
). However, it would be better to save these separately. Current implementation works, but is awkward, since there's a methodvoid saveMemberPropertiesWithoutViews(MemberProperties memberProperties);
which saves the MemberProperties, but not the viewReferences. This is needed since viewReferences are updated based on other events (and it's not guaranteed that they are later in time than the creation of MemberProperties). Hence, the need for a split :-)