We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-6219

Extend Spring Java-Config doc on how to lookup shared ProcessEngine

      Context:

      The current Spring Java-Config documentation shows how to bootstrap an embedded process engine.
      But there are also those people who want to use Spring Java-Config to lookup a shared process engine. When they use the provided example, they are retrieving a process engine bean using the @Bean annotation, for example:

      @Bean
      public ProcessEngine getDefaultProcessEngine() {
        return BpmPlatform.getDefaultProcessEngine();
      }
      

      This leads to the symptom that when the process application is undeployed and the Spring context is destroyed, the process engine is closed too because when a @Bean annotated bean is destroyed, its close() or destroy() method is called, if it has one. This is done implicitly by Spring. Related to the above code example, the default process engine is then closed and nothing works anymore, like Camunda webapps etc, until the server is restarted.

      AT:

      • Provide an explicit Java-Config example on how to create a shared process engine bean using @Bean-Annotation.

        This is the controller panel for Smart Panels app

            Loading...
            Uploaded image for project: 'camunda BPM'
            1. camunda BPM
            2. CAM-6219

            Extend Spring Java-Config doc on how to lookup shared ProcessEngine

                Context:

                The current Spring Java-Config documentation shows how to bootstrap an embedded process engine.
                But there are also those people who want to use Spring Java-Config to lookup a shared process engine. When they use the provided example, they are retrieving a process engine bean using the @Bean annotation, for example:

                @Bean
                public ProcessEngine getDefaultProcessEngine() {
                  return BpmPlatform.getDefaultProcessEngine();
                }
                

                This leads to the symptom that when the process application is undeployed and the Spring context is destroyed, the process engine is closed too because when a @Bean annotated bean is destroyed, its close() or destroy() method is called, if it has one. This is done implicitly by Spring. Related to the above code example, the default process engine is then closed and nothing works anymore, like Camunda webapps etc, until the server is restarted.

                AT:

                • Provide an explicit Java-Config example on how to create a shared process engine bean using @Bean-Annotation.

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        lipphardt Christian
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              lipphardt Christian
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              2 Start watching this issue

                                Created:
                                Updated:
                                Resolved: