dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #05471
Re: [Branch ~dhis2-devs-core/dhis2/trunk] Rev 1785: Audit trail logging functions for DataSet, OrganisationUnit, User modules.
Den 19. apr. 2010 kl. 18.17 skrev Viet Nguyen:
> About distinct audit logger, I don't know how to use two different loggers in one application... Unless I manually create a logger class ( create file, write logging message to that file....etc.. ) which I did before in my old project...
>
> Anyway...turning debug on and audit off....is not really a common use I think ... I always want to see everything when I turn debug on ...
> And when you are debugging , means that you don't work on production server, so it will not effect the production logging files...
> However, I will google more about using two different loggers in one application, should be interesting.
All it takes is just having a separate name for the audit log, as Bob says. If you want it to log to a separate file, you just configure a separate log4j log for that. But I agree with Bob, having an audit logger dependency injected, is better. After all, it is a business concern, and with an AuditLogger interface it will be trivial to change the implementation later, if that is required.
> Anyway ...I have to back with STQC bugs now ...so could we consider that committed code as a beta version of this audit trail logging ...
That sounds about right :) Good to have audit logging, at least!
Jo
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
References