Spring Configuration loading JDBC problem when consolidating multiple MAVEN projects

Description of the problem:

Both projects use JDBC to access the MySQL database, each running OK, but merged into a MAVEN project, found that the previous project access to the database exception, seemingly can't get their own DAO.

Workaround:

Found in the XML configuration of the two projects, there is a common bean, the bean ID is sqlmapclient, because spring is all the configuration files loaded together, so the later sqlmapclient, replaced the previous

Sqlmapclient, and because the two projects access to the MySQL library and table are different, resulting in the previous project JDBC access to MySQL library, so error. The solution is simple, change the two bean ID of the same name to be different, such as one is Sqlmapclient, the other is called SqlMapClient2

Spring Configuration loading JDBC problem when consolidating multiple MAVEN projects