[midPoint-git] [Evolveum/midpoint] 1a5ee3: Add resource based provider of correlation definition

[Andrej]

  Branch: refs/heads/feature/fast-simulation
  Home:   https://github.com/Evolveum/midpoint
  Commit: 1a5ee3495a557e85f07e4d9e16dff12b6e16ea88
      https://github.com/Evolveum/midpoint/commit/1a5ee3495a557e85f07e4d9e16dff12b6e16ea88
  Author: Andrej Zan <andrej.zan at evolveum.com>
  Date:   2025-11-15 (Sat, 15 Nov 2025)

  Changed paths:
    A model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/correlator/tasks/CorrelationDefinitionProvider.java
    A model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/correlator/tasks/ResourceCorrelationDefinitionProvider.java
    A model/model-impl/src/test/java/com/evolveum/midpoint/model/impl/correlator/tasks/ResourceCorrelationDefinitionProviderTest.java
    A model/model-impl/src/test/resources/correlator/correlation/merge/resource-dummy-correlation-in-attribute.xml
    A model/model-impl/src/test/resources/correlator/correlation/merge/resource-dummy-correlation-in-schema-handling.xml
    A model/model-impl/src/test/resources/correlator/correlation/merge/resource-dummy-correlation-in-synchronization.xml
    M repo/repo-test-util/src/main/java/com/evolveum/midpoint/test/AbstractIntegrationTest.java

  Log Message:
  -----------
  Add resource based provider of correlation definition

**What**

Implement the provider of a correlation definition which reads the
definition from the resource.

**Why**

For "fast" simulation of correlations, we want to add an option for
including also existing correlation definition into the simulation. For
that purpose we need to read the correlation definition from the
resource. The work definition of the correlation simulation activity may
also contain correlation definition (in fact that is the main point of
implementing the activity).

That, however, means we have at least two sources of correlation
definitions for the activity. How those sources are accessed and
processed can differ significantly. For example when we read correlation
definition from the resource, we need to "merge" correlations, which are
possibly defined by different structures on different places of the
resource.

Because of that this change introduce the "provider" abstraction which
allows to encapsulate logic specific to particular source of
correlations.

**Notes**

As mentioned above, the correlation in resource can be defined in more
ways. Some of them are legacy, but we still support them. The provider
of the correlation implements a logic which collects all those
structures and merges them to single correlation definition. To do that
it relies on `CorrelatorsDefinitionUtils`, which provides necessary
functionality.



To unsubscribe from these emails, change your notification settings at https://github.com/Evolveum/midpoint/settings/notifications