| commit | a8934462d79a4bfd2ab295016375bff0aa29377f | [log] [tgz] |
|---|---|---|
| author | Matt Sicker <boards@gmail.com> | Mon Jul 02 13:36:45 2018 -0500 |
| committer | Matt Sicker <boards@gmail.com> | Mon Jul 02 13:36:45 2018 -0500 |
| tree | e2058a1c6434636fd5fb59fce00986a2130af9bd | |
| parent | a8f8add5607a6c7af6c20627531fb2294c079dbc [diff] |
Use released version
This is a sample project that illustrates how to create cusom Audit Event classes and a custom Audit Service using Log4j-Audit.
The Audit Service API project contains the catalog that will be managed by the Log4j Catalog Web Application. That web application simply needs to be configured with the url of this project and the path to the JSON catalog within the project. Whenever a Maven build is run the catalog will be read and a new set of Java Interfaces will be generated. The interfaces can be used by Java applications to perform audit logging.
The Audit Service is a web application that allows applications (especially those not written in Java) to perform audit logging while still having ensuring that the audit events conform to the definitions in the catalog.