From ff278272f078f6d23758a6bac2e826d7d25ccc1d Mon Sep 17 00:00:00 2001
From: Lars Hamann <58341317+h-man2@users.noreply.github.com>
Date: Thu, 13 Jun 2024 14:11:39 +0200
Subject: [PATCH] fix: handling of result values for operation calls

- Aligned ExpInstanceConstructor to changes made by #80
---
 .../java/org/tzi/use/uml/ocl/expr/ExpInstanceConstructor.java  | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/use-core/src/main/java/org/tzi/use/uml/ocl/expr/ExpInstanceConstructor.java b/use-core/src/main/java/org/tzi/use/uml/ocl/expr/ExpInstanceConstructor.java
index e656f5db..d2899bcd 100644
--- a/use-core/src/main/java/org/tzi/use/uml/ocl/expr/ExpInstanceConstructor.java
+++ b/use-core/src/main/java/org/tzi/use/uml/ocl/expr/ExpInstanceConstructor.java
@@ -83,6 +83,7 @@ public Value eval(EvalContext ctx) {
 
         MOperationCall operationCall = new MOperationCall(this, self, constructor, arguments);
         operationCall.setPreferredPPCHandler(ExpressionPPCHandler.getDefaultOutputHandler());
+        operationCall.setResultValue(result);
 
         MSystem system = ctx.postState().system();
         try {
@@ -93,7 +94,7 @@ public Value eval(EvalContext ctx) {
         } finally {
             try {
                 if (operationCall.enteredSuccessfully()) {
-                    system.exitQueryOperation(ctx, result);
+                    system.exitQueryOperation(ctx);
                 }
             } catch (MSystemException ignored) {
             }