AuditLog, a logger specifically for auditing, has been released as a plugin of LimpidLog. LimpidLog is a logging system which does not require any hard-coded log statements. It records important information about the execution of a class at runtime when the class is registered. It is primarily meant to log data for debugging purposes. Both LimpidLog and AuditLog are open source projects with GPL license at http://www.acelet.org. SuperLog is released as a full logging system combining both LimpidLog and AuditLog under one roof. A Swing manager can be used to dynamically manage your applications. Logged data can be read by human, or read my LimpidDebugger which interprets the data presents it as source level debugging. SuperLogReader is a log reader with color syntax highlighting for log data.

It records important information about the execution of a class at runtime when the class is registered.

What do you mean by registering a class ? , does this utility intercept class loading ?

It is primarily meant to log data for debugging purposes.

How can it then be used as a production worthy auditing tool? Your website states "Log for auditing is part of business logic of the application" Most financial system have a regulatory requirement to audit user actions and the transaction information, how can that be achieved using AuditLog ?

It records important information about the execution of a class at runtime when the class is registered.

What do you mean by registering a class ? , does this utility intercept class loading ?

It is primarily meant to log data for debugging purposes.

How can it then be used as a production worthy auditing tool?

Your website states "Log for auditing is part of business logic of the application"
Most financial system have a regulatory requirement to audit user actions and the transaction information, how can that be achieved using AuditLog ?

Register a class means: you tell LimpidLog to log (record) runtime information about the class. You can register a class using included GUI tool by clicking. LimpidLog use -javaagent option of java.lang.instrument.Instrumentation to manage Java classed. It is JVM which loads-reloads Java classes. There are two different things here: log for auditing and log for debugging. LimpidLog is log for debugging. 90% of application logging is logging for debugging. LimpidLog is an alternative for traditional logging statements. AuditLog is for auditing. Currently many applications use JDK logging or Log4J to do that. AuditLog is an alternative for traditional logging, like JDK logging or Log4J. For example, you may simple print out for auditing: System.out.println("User login: " + userName); AuditLog allows you to log such information with LimpidLog. With both AuditLog and LimpidLog you can log all information you want, still have all benefits of LimpidLog.

Thank you for your answers. Nagraj