SSH integration-jar package conflict

Document directory

• Exception: Error creating bean with name 'sessionfactory 'defined in servletcontext resource [/WEB-INF/classes/applicationcontext. ">

Well, at, there is a problem with SSH integration, that is, when using myeclipse to import packages, it is not clear which functional modules have which packages,

Then, the first version of the dormitory appears.

Exception: Error creating bean with name 'sessionfactory 'defined in servletcontext resource [/WEB-INF/classes/applicationcontext. ">

I guess it is to import redundant packages, resulting in a jar package conflict. On the left of the following is the correct jar package diagram. On the right, there is a wrong jar package diagram.

In comparison, what are the multiple jar packages and what are possible causes ~~)? Unknown role

Aopalliance. Jar (?) --- Combination of the AOP Alliance AOP package ~~ Dizzy

ASM. Jar (this is not redundant, just as a comparison with the following)

Asm-2.2.3.jar okay -- write this, jar package conflict is strange ~~~~~!!

Asm-commons-2.2.3.jar

Asm-util-2.2.3.jar

Aspectjlib. Jar <! -- The following aspectj series all belong to the jar packages required by AOP -->

Aspectjrt. Jar

Aspectjweaver

Cglib-nodep-2.1_3.jar

Spring-aop.jar

Spring-agent.jar

Spring-tomcat-weaver.jar

After comparing the package with a runable project and changing it to the same one, The project runs successfully ..

In fact, it is estimated that

ASM. Jar

Asm-2.2.3.jar

Conflicts between the two jar packages. Many people on the Internet have encountered the same problems as me.