Announcement Announcement Module
Collapse
No announcement yet.
BeanNameAutoProxyCreator referencing non-existent bean Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • BeanNameAutoProxyCreator referencing non-existent bean

    If the BeanNameAutoProxyCreator references a non existent bean
    in its 'beanNames' list, it silently ignores it.
    This caused few hours of debugging to finally spot that there was a case difference that was causing a bean not to get proxied.

    Throwing the NoSuchBeanDefinitionException in such case is probably what the BeanNameAutoProxyCreator should havw done.

    Best Regards,

    Emil Marceta

  • #2
    Please fill a request on JIRA.

    Comment


    • #3
      Re: BeanNameAutoProxyCreator referencing non-existent bean

      Turns out that the BeanNameAutoProxyCreator 'beanNames' property is actually a pattern and not explicit bean name. The proxy is applied to the match result that may be 0 or or more bean definitions.

      There might be an argument to be made about a a better property name to describe it is actually a name pattern.

      Comment

      Working...
      X