Development using Tomcat production using WebLogic causes jar package conflicts to be resolved?

Problem description
A jar package was added at development time, and when the delta package is deployed to the test server, the following error message appears when launching the app:
Java.lang.LinkageError:loader constraint Violation:loader (instance of weblogic/utils/classloaders/ Changeawareclassloader) previously initiated loading for a different type with name "Org/w3c/dom/typeinfo"
Note: Development uses Tomcat and the test server uses WebLogic.
Cause of error
The WebLogic comes with a jar package that conflicts with the project's jar package.
Error message
Under any class file in Project engineering, change the Org/w3c/dom/typeinfo to Org.w3c.dom.TypeInfo to see the information for this jar: (Crtl+typeinfo). Locate the conflicting jar package (Xmlbeans-2.3.0.jar).

Solutions (three types)
1. Delete Project projects under the JAR package

Because the project's weblogic.xml configuration is the jar package under the priority load project, delete the Xmlbeans-2.3.0.jar package under Project Engineering, and then redeploy or restart the app.
[Email protected] ~/sbin]$ sh redeploy.sh mobileproj

2. Delete the associated Xmlbean jar package under WebLogic

This is not recommended because it is possible that other items are under WebLogic with this jar package, and it is time consuming to find the jar packet conflict information under WebLogic.

3. Configure Weblogic.xml
Deleting the configuration of the priority loaded project jar or setting to false is not recommended because there may be other jar packages that are in conflict with night.

Development using Tomcat production using WebLogic causes jar package conflicts to be resolved?