Class OperationExecutionRecorderForTasks


  • @Component
    public class OperationExecutionRecorderForTasks
    extends Object
    Prepares complex OperationExecutionType records for search-iterative and live-sync/async-update tasks. Uses OperationExecutionWriter for the actual writing of the records.
    • Constructor Detail

      • OperationExecutionRecorderForTasks

        public OperationExecutionRecorderForTasks()
    • Method Detail

      • recordOperationExecution

        public void recordOperationExecution​(OperationExecutionRecorderForTasks.Target target,
                                             RunningTask task,
                                             String partUri,
                                             OperationResult result)
        Writes an operation execution record.
        Parameters:
        target - Where to write the record to.
        task - Related task. It could be any task that has the correct root task OID filled-in.
        partUri - URI of the task part in context of which the processing took place.
        result - Combined use: (1) This is the result that we want to write to the object (i.e. it must have already computed status and message. (2) This is the result we use for our own writing operations. We hope these two usages are not in conflict. If so, they will need to be split. TODO implement redirection also for (rightfully) deleted objects? Currently deleteOk=true means no exception is propagated from the writer. Overall, it is questionable if we want to write such information at all. TODO move redirection to the writer level?