Fix profile determination in function calls

Argument evaluation was done with the wrong profile.
Evolveum · Aug 10, 2023 · f43994a · f43994a
1 parent c3d02fa
commit f43994a
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/.../com/evolveum/midpoint/model/common/expression/evaluator/FunctionExpressionEvaluator.java b/.../com/evolveum/midpoint/model/common/expression/evaluator/FunctionExpressionEvaluator.java
@@ -126,8 +126,9 @@ public PrismValueDeltaSetTriple<V> evaluate(ExpressionEvaluationContext context,
 
                 Expression<V, D> argumentExpression = context.getExpressionFactory()
                         .makeExpression(
-                                argumentExpressionCI, argumentValueDefinition,
-                                ExpressionProfile.none(), // a profile should be set in the context
+                                argumentExpressionCI,
+                                argumentValueDefinition,
+                                context.getExpressionProfile(), // this is the caller's profile
                                 shortDesc, context.getTask(), argumentResult);
 
                 PrismValueDeltaSetTriple<V> argumentValueTriple = argumentExpression.evaluate(context, argumentResult);
@@ -137,8 +138,7 @@ public PrismValueDeltaSetTriple<V> evaluate(ExpressionEvaluationContext context,
 
                 functionVariables.addVariableDefinition(argumentName, argumentValue, argumentValueDefinition);
 
-            } catch (SchemaException | ExpressionEvaluationException | ObjectNotFoundException | CommunicationException
-                    | ConfigurationException | SecurityViolationException e) {
+            } catch (Exception e) {
                 argumentResult.recordException("Failed to resolve argument: " + argumentName + ". Reason: " + e.getMessage(), e);
                 throw e;
             } finally {