Announcement Announcement Module
Collapse
No announcement yet.
Autoproxy problems upgrading from 1.2.1 to 1.2.2 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Autoproxy problems upgrading from 1.2.1 to 1.2.2

    My application worked fine under 1.2.1. However, I upgraded to 1.2.2 this morning and now the majority (if not all) of my singletons are now reporting:
    "Bean 'XXXXX' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying"

    Any ideas?

    Mike

  • #2
    Check the changelog carefully and see what were the changes.
    You can find it here: http://static.springframework.org/sp.../changelog.txt

    Comment


    • #3
      Ok, so I looked closely and found the following changes that could be causing the problem:

      * fixed AbstractAutowireCapableBeanFactory to not track dependencies for passed-in existing beans (avoiding memory leak)
      * fixed DefaultListableBeanFactory to exclude bean definitions with factory method from pre-instantiation type matching
      * fixed DefaultListableBeanFactory to pre-instantiate and match beans with factory method / "factory-bean" definition
      Though I don't have any idea why any of those changes would have made what used to work in 1.2.1 not work in 1.2.2. I'm going to need more hints.

      Mike

      Comment


      • #4
        I think you can report this issue on JIRA.

        Comment

        Working...
        X