Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Add Option for Process Specific Spring Context #262

Open
hhund opened this issue Sep 2, 2021 · 1 comment
Open

Add Option for Process Specific Spring Context #262

hhund opened this issue Sep 2, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@hhund
Copy link
Member

hhund commented Sep 2, 2021

We should add an option to configure which spring beans are needed for with process inside a process plugin. Some of the configured beans might only be needed by specific processes and initializing them, while the specific process is excluded and not configured might make configuration more complex.

One option could be to use Spring profiles with a name that corresponds to the process name. If no profile is defined the bean would be active by default, if a profile is defined, the bean would only be active if a process with the same name is active as well.

@hhund
Copy link
Member Author

hhund commented Oct 27, 2021

The logic deciding which process to activate or not is run after the spring application contexts for the process plugins are initialized since java delegate classes are needed during process deployment by the camunda bpe. Implementing #262 may not be possible. Implementing #261 should allow process plugins to run custom logic after the plugins has been deployed and the state of a specific process from a process plugin is known.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant