[midPoint-git] [Evolveum/midpoint] 54db56: Partially fix MID-4474: skipped triggers

[Pavol Mederly]

  Branch: refs/heads/post-3.7-fixes
  Home:   https://github.com/Evolveum/midpoint
  Commit: 54db569305a7f6f68d0e8350e95defcf04209942
      https://github.com/Evolveum/midpoint/commit/54db569305a7f6f68d0e8350e95defcf04209942
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2018-02-23 (Fri, 23 Feb 2018)

  Changed paths:
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/sync/FocusValidityScannerTaskHandler.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/trigger/TriggerScannerTaskHandler.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/util/AbstractScannerTaskHandler.java
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/AbstractConfiguredModelIntegrationTest.java
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/TestDeputy.java
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/TestTriggerTask.java
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/sync/TestValidityRecomputeTask.java
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/util/MockTriggerHandler.java
    M model/model-test/src/main/java/com/evolveum/midpoint/model/test/AbstractModelIntegrationTest.java
    M repo/repo-common/src/main/java/com/evolveum/midpoint/repo/common/task/AbstractSearchIterativeResultHandler.java
    M repo/repo-test-util/src/main/java/com/evolveum/midpoint/test/Checker.java
    M repo/task-quartz-impl/src/test/java/com/evolveum/midpoint/task/quartzimpl/TestQuartzTaskManagerContract.java

  Log Message:
  -----------
  Partially fix MID-4474: skipped triggers

Triggers and validation boundaries might get skipped if the trigger
or validity scanner task is brought down (via suspend or midPoint
shutdown) while processing objects. The reason is that
lastScanTimestamp is updated even if not all objects were processed.

Here we fix that. For validity boundaries it means that some of them
will be processed twice (after next task run); but it should be
harmless. Triggers are OK, as they are deleted just after being
processed.