Problem Description:
Native Windows myeclipse10.7 runs a non-maven Java project, where some classes are injected using SPRING3 annotations, scanned using a configuration file Component-scan, and everything works in the native debug test, But when it hits a jar and puts it on a Linux server, it always says: Org.springframework.beans.factory.NoSuchBeanDefinitionException:No Bean named ' XXXX ' is Defined
Check the note name, configuration file, file encoding, and modify the configuration and so on try to not solve after the online browsing all kinds of data finally solved, here to make notes.
This machine's class file is directly compiled into the class directory for direct drinking, Component-scan can directly scan the class directory, but packaged into a jar Spring3 Component-scan will not be scanned, actually not scanning Instead, there is a DD entity directory (add entity directory) attribute when hitting the jar package, which needs to be checked as
Spring Auto Scan does not support jar packages <component-scan>