Reimplement audit and security using HierarchyManagerWrapper, ContentWrapper,
etc.
----------------------------------------------------------------------------------
Key: MAGNOLIA-2730
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2730
Project: Magnolia
Issue Type: Improvement
Components: core
Reporter: Grégory Joseph
Assignee: Philipp Bärfuss
Fix For: 4.1, Green
This would simplify:
* turning these features on/off
* replacing/customizing them
* tests (because I don't want to have audit log in my tests, nor have to
configure them)
We already have RepositoryAcquiringStrategy, which is where the appropriate
wrappers w/c/ould be constructed.
It would also serve as a proof of concept for more advanced uses of wrappers
(which I will dutifully note here once I remember them)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
