Uploaded image for project: 'Spring Integration'
  1. Spring Integration
  2. INT-3640

Some components trigger BeanPostProcessorChecker warning "is not eligible for getting processed by all BeanPostProcessors"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Complete
    • Affects Version/s: 4.1.2
    • Fix Version/s: 4.2 M1
    • Component/s: Core
    • Labels:
      None
    • Environment:
      Java 7, Spring Framwork 4.1.4

      Description

      Using Spring Framwork 4.1.4 + Spring Integration 4.1.2 triggers the warning from BeanPostProcessorChecker about early configuration of bean and their inability to be processed by BeanPostProcessors.

      This happens even with a very trivial app consisting only of a inbound stdin adapter, a channel and a poller: add <int:annotation-config/> to the context XML and you'll get the warning. Same thing happens using AnnotationConfigApplicationContext and the @EnableIntegration annotation (since both it and the xml directive just defers to IntegrationRegistrar).

      I've created a simple project on GitHub to reproduce the problem.

      2015-02-13 16:53:35,587 [main] INFO o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'integrationGlobalProperties' of type [class org.springframework.beans.factory.config.PropertiesFactoryBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
      2015-02-13 16:53:35,588 [main] INFO o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'integrationGlobalProperties' of type [class java.util.Properties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
      2015-02-13 16:53:35,588 [main] INFO o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'messageBuilderFactory' of type [class org.springframework.integration.support.DefaultMessageBuilderFactory] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
      2015-02-13 16:53:35,651 [main] INFO o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean '(inner bean)#406fcc9c' of type [class org.springframework.integration.channel.MessagePublishingErrorHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
      2015-02-13 16:53:35,651 [main] INFO o.s.scheduling.concurrent.ThreadPoolTaskScheduler - Initializing ExecutorService 'taskScheduler'
      2015-02-13 16:53:35,653 [main] INFO o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'taskScheduler' of type [class org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
      2015-02-13 16:53:35,653 [main] INFO o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'integrationHeaderChannelRegistry' of type [class org.springframework.integration.channel.DefaultHeaderChannelRegistry] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              Assignee:
              abilan Artem Bilan
              Reporter:
              gdelprete Gabriele Del Prete
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: