[midPoint-git] [Evolveum/midpoint] 083c11: Modify work definition of mapping simulation activity

Andrej noreply at github.com
Tue Feb 10 14:28:14 CET 2026


  Branch: refs/heads/master
  Home:   https://github.com/Evolveum/midpoint
  Commit: 083c1159b4700988478eaf7c14a4efb2f1ae9cba
      https://github.com/Evolveum/midpoint/commit/083c1159b4700988478eaf7c14a4efb2f1ae9cba
  Author: Andrej Zan <andrej.zan at evolveum.com>
  Date:   2026-02-10 (Tue, 10 Feb 2026)

  Changed paths:
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/util/task/work/WorkDefinitionUtil.java
    M infra/schema/src/main/resources/xml/ns/public/common/common-tasks-3.xsd
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/mappings/tasks/MappingActivityHandler.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/mappings/tasks/MappingActivityRun.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/mappings/tasks/MappingWorkDefinition.java

  Log Message:
  -----------
  Modify work definition of mapping simulation activity

**What**

Create new complex type, which holds necessary data for the mappings
simulation. In particular it specifies mappings alongside the item path
they are supposed to map.

**Why**

Previous definition contained mapping definition, but that does not
contain information about what item it is mapping. But that is crucial
information to evaluate the mapping on a correct item.

**Notes**

This change also fixed few `since` annotations, because they had wrong
version set.

**Task**: 10992


  Commit: e58f65a2a00cad811cfff7e0853f4bee327b6fb0
      https://github.com/Evolveum/midpoint/commit/e58f65a2a00cad811cfff7e0853f4bee327b6fb0
  Author: Andrej Zan <andrej.zan at evolveum.com>
  Date:   2026-02-10 (Tue, 10 Feb 2026)

  Changed paths:
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/focus/InboundProcessor.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/focus/inbounds/AbstractInboundsProcessing.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/focus/inbounds/FullInboundsProcessing.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/lens/projector/focus/inbounds/SingleShadowInboundsProcessing.java

  Log Message:
  -----------
  Return deltas computed by inbound processing

**What**

Instead of applying the computed delta to the target object directly in
the `AbstractInboundsProcessing` class, move this responsibility to the
caller of inbound processing implementations.

**Why**

Main reason is, that I want to use inbound processing implementation in
the mappings simulation activity. But in there, I need the deltas, not
the target object with them already applied, because I need to write
those deltas to the simulation result. Other option would be to diff the
object with applied deltas with the original object. But that is a waste
of resources.

There is also other reason. The `executeToDeltas` method, originally
computed the deltas, but it also applied them to the target object. But
that is quite counter-intuitive. Considering the method name, I would
expect it will just compute and return the deltas.

By moving the application of the deltas outside, we also gain more
flexibility, because the way how deltas are applied does not need to be
defined by the implementations. That means, the deltas produced by one
implementation, can be used in different ways, depending on the
requirements of the caller.

**Task**: 10992


Compare: https://github.com/Evolveum/midpoint/compare/bbe75b0fd1c6...e58f65a2a00c

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


More information about the midPoint-svn mailing list