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

Check (and probably retire) ZeebeExpressionResolver #208

Closed
berndruecker opened this issue Jun 2, 2022 · 2 comments
Closed

Check (and probably retire) ZeebeExpressionResolver #208

berndruecker opened this issue Jun 2, 2022 · 2 comments

Comments

@berndruecker
Copy link
Contributor

Why is this needed and can we probably remove it?

@jangalinski
Copy link
Collaborator

Honestly: can't remember ... I guess I needed a component that is not public in zeebe core so I created a copy ... but if everything continues working without it ... remove.

@lzgabel
Copy link
Contributor

lzgabel commented Jun 20, 2023

Hi Guys. @jangalinski, @berndruecker. Why did we remove this? 😭

In the previous version, we started different projects in different environments and could dynamically set the type of JobWorker by parsing the configuration file. However, this feature has been removed at present.

@JobWorker(type = "close-${close-job.env}-${close-job.work-name}”)
public Object handle(final @VariablesAsType UserData data) {
....
}

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

3 participants