IMO we could throw a runtime exception instead of just logging a warning message. In case of applying modifications outside of an active transaction, historical data would not be flushed to audit tables (AuditProcess#doBeforeTransactionCompletion(SessionImplementor) not executed), which is more serious issue. Adam, what do you think?
IMO we could throw a runtime exception instead of just logging a warning message. In case of applying modifications outside of an active transaction, historical data would not be flushed to audit tables (AuditProcess#doBeforeTransactionCompletion(SessionImplementor) not executed), which is more serious issue. Adam, what do you think?