Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
5.1 EE SP4 (5.1.7), 5.2 EE SP2 (5.2.6)
-
None
-
None
-
All
Description
The order in which *LocalServiceImpl classes implement add(), delete() and update() has been standardized. This standardization will address inconsistency issues such as the following:
- Model listeners do not always have access to Expando attributes
- When a social activity is logged
- Emails/subscriptions are sometimes sent before an entry has been saved
The new ordering when adding/updating:
expando, model, resource, portal package, local package, other package, indexer, status, file, email / subscribers, ping
The new ordering when deleting:
model, resource, portal package, local package, other package (expando is in here) indexer, status, file, email / subscribers, ping
Attachments
Issue Links
- is related to
-
LPS-6584 Refactor the order in which code blocks are executed for *ServiceImpl.add / update
- Closed