Dec 12th, 2012, 06:51 AM
NoSuchBeanDefinitionException: No bean named
I have two standalone applications based on Spring, each one of them has a application context. I have two jar packets building with maven-shade-plugin. This app's are used on a web application like external libraries. My problem is that if I include the two jar applications with different application context, the beans of the first application thrown the error "NoSuchBeanDefinitionException: No bean named" when the global app does reference at it.
How can I fixed this error?