In actual projects, the original large projects need to be split into small functions based on business functions, and deployed independently in the form of services. On this premise, the same code is also used to apply various projects, for convenience. It is introduced as a jar package and used as another project. In an independent JAR package, we set an independent data source file to map objects. However, during project integration, the configuration file and object ing cannot be loaded. We use JPA object ing in all object files. @ Entity in specific use, the unkonwn entity xxxx exception is thrown for two reasons: 1. web. in xml, you must specify classpath *: applicationContext -*. xml, especially classpath *, scans the configuration file in the jar package. Otherwise, only the projects under the add-on directory are displayed. 2. In the persistence. xml file, you must specify that the file of the JAR package is located at the same level as the node provider. Set jar-file to specify an absolute directory or file.