[overlord-issues] [JBoss JIRA] (SRAMP-197) Auditing: re-implement *not* using JCR observer pattern

Eric Wittmann created SRAMP-197: ----------------------------------- Summary: Auditing: re-implement *not* using JCR observer pattern Key: SRAMP-197 URL: https://issues.jboss.org/browse/SRAMP-197 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Core Affects Versions: 0.2.0 - Security & S-RAMP-1.0 Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.3.0 - JBPM6 Integration Re-write the core auditing to no longer use the JCR observer pattern. The JCR observer pattern introduces a number of challenges, including: 1) async processing of auditing information. this is problematic in a number of ways, but most importantly is that data may be lost due to slower processing of the auditing information than the information on the artifact itself. Since the JCR observation events don't contain before and/or after values for changes, we have to go after the data directly. If changes happen quickly (before the observer has a crack at it) then data may be lost. 2) multi-phase processing of artifact adds/updates in the jcrpersistence impl -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira