We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
We couldn't load the project sidebar. 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-10863 Provide Spring Boot External Task Client as part of Spring Boot Starter
  3. CAM-13286

Spring logs configuration hint when BeanFactoryPostProcessor beans are not exposed via static method

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.15.0-alpha5, 7.15.0
    • None
    • None
    • None

      Problem

      Spring logs the following:

      [main] INFO org.springframework.context.annotation.ConfigurationClassPostProcessor - Cannot enhance @Configuration bean definition 'org.camunda.bpm.client.spring.impl.PostProcessorConfiguration' since its singleton instance has been created too early. The typical cause is a non-static @Bean method with a BeanDefinitionRegistryPostProcessor return type: Consider declaring such methods as 'static'.

      Solution

      Define bean methods that return a type assignable to BeanFactoryPostProcssor as static

        This is the controller panel for Smart Panels app

            Loading...
            Uploaded image for project: 'camunda BPM'
            1. camunda BPM
            2. CAM-10863 Provide Spring Boot External Task Client as part of Spring Boot Starter
            3. CAM-13286

            Spring logs configuration hint when BeanFactoryPostProcessor beans are not exposed via static method

            XMLWordPrintable

              • Icon: Sub-task Sub-task
              • Resolution: Fixed
              • Icon: L3 - Default L3 - Default
              • 7.15.0-alpha5, 7.15.0
              • None
              • None
              • None

                Problem

                Spring logs the following:

                [main] INFO org.springframework.context.annotation.ConfigurationClassPostProcessor - Cannot enhance @Configuration bean definition 'org.camunda.bpm.client.spring.impl.PostProcessorConfiguration' since its singleton instance has been created too early. The typical cause is a non-static @Bean method with a BeanDefinitionRegistryPostProcessor return type: Consider declaring such methods as 'static'.

                Solution

                Define bean methods that return a type assignable to BeanFactoryPostProcssor as static

                  This is the controller panel for Smart Panels app

                        tassilo.weidner Tassilo Weidner
                        tassilo.weidner Tassilo Weidner
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              tassilo.weidner Tassilo Weidner
                              tassilo.weidner Tassilo Weidner
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              2 Start watching this issue

                                Created:
                                Updated:
                                Resolved: