Preferred Way to use Process Application Event Listener

Camunda 7 Topics Discussion & Questions
3

Hi Jan (@jangalinski) ,

thanks for your answer. In my case it is not about general Events but about the specific Camunda Process Application Event Listener. Actually it is about implementing ProcessApplicationInterface and overwriting the getExecutionListener and getTaskListener methods.

This was done so far by extending SpringBootProcessApplication which in the end extended AbstractProcessApplication (implementing the ProcessApplicationInterface). I find this very useful, e.g. in my camunda-variable-scope-demo example.

/**

  • The core Spring Application configuration.
    */
    @SpringBootApplication
    @ProcessApplication
    public class Main extends SpringBootProcessApplication {
@Override
public ExecutionListener getExecutionListener() {
    return new GlobalExecutionListener();
}

public static void main(final String... args) {
    SpringApplication.run(Main.class, args);
}

}

This does not work anymore if I replace the @ProcessApplication annotation with @EnableProcessApplication.

I guess in my case it makes sence to stay on the old style of configuration. I would appreciate if both “Get started” configurations would be mentioned in the documentation. And not only in the ReadMe file but also (or above all) in the documentation. Currently only links to some sample projects are mentioned here.

Thanks and keep up with the good work!

Franz