8/11/2012 2:50:24 PM
audit logs are recorded for an object which has a history
table, DefaultAuditDao needs to fetch the record ids from the history
table, not the main table itself.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
8/11/2012 2:45:20 PM
table exists, we record audit logs on the history
table itself, not the main one (e.g. ACCOUNT_HISTORY or TAG_HISTORY).
payment wasn't respecting this convention.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
8/10/2012 4:03:22 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
8/10/2012 3:48:47 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
8/10/2012 3:38:53 PM
audit logs for various objects.
This uses the newly introduced container objects for audit logs.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
8/10/2012 2:55:15 PM
in AuditDao
We don't lookup by record id, but by id.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
|
|
8/10/2012 2:37:08 PM
audit logs in the JAX-RS APIs, it becomes clear
that we need some sort of objects to manipulates these logs.
This patch introduces the first version of these objects. No doubt the
interfaces will evolve as we use them more and more. This first pass
simply maps object ids to a list of AuditLog objects.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
|
|
|
|
