-
Improvement
-
Resolution: Won't Do
-
Major
-
None
-
4.0
-
None
-
None
Currently only after all data is gathered, AuditLoggingManager is called. It should be possible to instrument all the aspects of logging even obtaining user name as in some situations (startup, installation) such data might not be available and attempt to obtain them causes chain of failures (nice example is recent update of node types in user workspace ... can't really read user names while manipulating the nodes representing users themselves).
Acceptance criteria
- is related to
-
MAGNOLIA-2600 Check exception handling in AuditLoggingUtil
- Closed
-
MAGNOLIA-2730 Reimplement audit and security using HierarchyManagerWrapper, ContentWrapper, etc.
- Closed