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

Retrieve JobId from ExecuteJobsCmd in camunda engine #4466

Open
kmannuru opened this issue Jul 1, 2024 · 4 comments
Open

Retrieve JobId from ExecuteJobsCmd in camunda engine #4466

kmannuru opened this issue Jul 1, 2024 · 4 comments
Assignees
Labels
type:feature Issues that add a new user feature to the project.

Comments

@kmannuru
Copy link

kmannuru commented Jul 1, 2024

User Story (Required on creation)

We have a couple of job interceptor use cases that need to get the jobId from ExecuteJobsCmd but it's protected and has no getter. We're using reflection to get it now,  but I would like to add a getter to https://github.com/camunda/camunda-bpm-platform/blob/master/engine/src/main/java/org/camunda/bpm/engine/impl/cmd/ExecuteJobsCmd.java

Functional Requirements (Required before implementation)

JobId is exposed as getter from ExecuteJobsCmd

Technical Requirements (Required before implementation)

Create a getter to return the JobId from ExecuteJobsCmd
@kmannuru kmannuru added the type:feature Issues that add a new user feature to the project. label Jul 1, 2024
@kmannuru
Copy link
Author

kmannuru commented Jul 1, 2024

I am working on this enhancement.

@venetrius venetrius self-assigned this Jul 5, 2024
@venetrius
Copy link
Member

Hi @kmannuru ,

We have understood your request and will now decide how we continue with your idea.

Cheers,

Gergely

@kmannuru
Copy link
Author

@venetrius Any update on this?

@venetrius
Copy link
Member

Hi @kmannuru,
org.camunda.bpm.engine.impl.cmd.ExecuteJobsCmd is an external API. It is advised to use external API-s when building upon Camunda as internal API-s can change upon new releases.

Having said that, could you help me understand why do you need to access the jobId in a job interceptor.
What is the high level idea, what are you trying to achieve with the job interceptor?
How do you define your job interceptor?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature Issues that add a new user feature to the project.
Projects
None yet
Development

No branches or pull requests

2 participants