Record it:
09:33:28 CSTClass path resource [Applicationcontext.xml]
Loading XML Bean Definitions from class path resource [Applicationcontext.xml] today the little buddy is having this problem.
The reason is that after the spring project is created, there is a lack of problems caused by the log jar, so you only need to import the appropriate log jar.
Log jar correlation:
Commons-logging: Avoid direct coupling with specific log schemes, decoupling via unified interface.
LOG4J: The most typical log solution. The specific log system. The output of the final log is reached by SLF4J-LOG4J12 initialization of the log4j.
SLF4J Logging facade for Java: A simple log façade for Java. The SLF4J portal is a collection of many interfaces, all of which are defined in SLF4J-API
( Note: Do not appear at the same time when importing multiple implementations of slf4j , otherwise the compilation will be an error )
Slf4j-api: Essentially SLF4J-API is an interface definition
SLF4J-LOG4J12: Link Slf4j-api and log4j in the middle of the adapter, the implementation of the Slf4j-apiz Staticloggerbinder interface, so that at compile time binding is SLF4J-LOG4J12 Getsingleton () method
In the Mybatis+spring project, the habit of directly copying into these jars
The record points drip, though insignificant.
Error when starting project: Loading XML Bean Definitions from class path resource [Applicationcontext.xml]