Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems mixing @Variable and @VariablesAsType parameters in same signature #421

Open
theseventhwave opened this issue Apr 28, 2023 · 0 comments

Comments

@theseventhwave
Copy link

When defining a @Jobworker, we find the following:

  1. If all parameters are declared @variable --> values are passed correctly (e.g., foobar( @variable a, @variable b ))
  2. If all parameters are declared @VariablesAsType --> values are passed correctly (e.g., foobar( @VariablesAsType a, @VariablesAsType b ) )
  3. If some parameters are @variable and others @VariablesAsType --> @VariablesAsType values are missing (e.g., foobar( @variable a, @VariablesAsType b ) )

Looking closer, we see that as soon as a @variable parameter is used, all non-@variable (i.e., @VariablesAsType) parameters are missing from ActivatedJob: getVariablesAsMap() and getVariables() bear witness to this. Stepping through the code shows that this seems to happen fairly deep in the system; possibly even prior to spring-zeebe (not sure).

This is not a problem in the engine: all parameters are shown correctly in Operate.

Invoking getVariablesAsMap().get() and getVariablesAsType() does not trigger this behavior, so it must be something else.

The versions tested are:

Zeebe 8.1.8
Spring-Zeebe 8.2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant