I'm not very satisfied about the design of this event since there are optional methods that will return null in most of the case. This will need some work to clean it up especially if we want to introduce a more sequential reporting action rather than a packet error reporting. This will allow for example to follow the process quickly in an interface or a servlet (yep, that's cool to run a check via a web interface in a source repository ;-) @author Stephane Bailliez @see AuditListener
This interface defines an abstract audit-event. Specifying events as interface aims at several optimized implementations. A simple one can be found at AuditEventImpl
.
This interface also defines several event properties, which are beyond the set of variables supported by.
@author Christian Bockermann <chris@jwall.org>Users can inject a {@link AuditEventRepository} to publish their own events oralternatively use Spring's {@link ApplicationEventPublisher} (usually obtained byimplementing {@link ApplicationEventPublisherAware}) to publish AuditApplicationEvents (wrappers for AuditEvent). @author Dave Syer @see AuditEventRepository
|
|
|
|
|
|
|
|