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

Improve Spring Zeebe docs for newbies #216

Open
1 of 3 tasks
berndruecker opened this issue Aug 1, 2022 · 3 comments
Open
1 of 3 tasks

Improve Spring Zeebe docs for newbies #216

berndruecker opened this issue Aug 1, 2022 · 3 comments
Assignees

Comments

@berndruecker
Copy link
Contributor

berndruecker commented Aug 1, 2022

Could be improved (raised by @ingorichtsmeier )

  • Make clear that only Spring Beans can be ZeebeWorkers (@Componnent, ...)
  • Improve explanation around variable handling / creating a good method signature (implement JobHandler vs. @ZeebeVariable, autoComplete, ...)
  • Existing Starter and Worker examples are not sufficient / not properly designed (e.g. main method including workers) --> align with best practices e.g. shown in TwitterExample. Maybe make one project out of it.
@HanselIdes
Copy link

Recommendation: align the formatting with the downloaded format/GSG repo
Example: change zeebe.client.cloud.client-id to zeebe.client.cloud.clientId

@odranoelBR
Copy link

odranoelBR commented Oct 6, 2022

Hi @berndruecker .
Tks for the client, awesome!!!

I'm stuck with some points before finish a poc to present in my company, that i think this improvments will help, like :

  1. How can i get current job from an instance id ? With workers is documented. Without a worker ? just an spring rest controller / service ?
  2. After get this job, how can i complete it ?
  3. After get this job, how can i get the form key?

@marcosdiez
Copy link
Contributor

I did my part to have this issue fixed here: #449

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

5 participants