[MAGNOLIA-7365] Improve MgnlAuditLoggingContentDecoratorSessionWrapper make it configurable or allow other interceptors involve Created: 31/Aug/18  Updated: 31/Aug/18

Status: Open
Project: Magnolia
Component/s: core
Affects Version/s: 5.7.1
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Viet Nguyen Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLHARDLK-74 Locked pages using JCR native API can... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   
  • As we would like to have our custom decorators to JR content follow Magnolia way and we're stuck with MgnlAuditLoggingContentDecoratorSessionWrapper. Since DefaultRepositoryManager is a Magnolia provided final class which having hard call to MgnlAuditLoggingContentDecoratorSessionWrapper that we cannot change, extends or configure it. So we're expecting to have a mechanism to configure it or implement event listeners / handlers before and after node changes for audit.
  • Suggestion:
  • For each node / property operation, we support before change and after change interceptors.
  • For each interceptor, we support synchronous / asynchronous handlers to those events.
  • Then to support custom action and transactional action, we'll register our custom content listener before apply any change based on our need.

Generated at Mon Feb 12 04:23:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.