Home > Back-end >  Weblogic: Java. Lang. ClassNotFoundException: com. Mysema. Query. DML. UpdateClause
Weblogic: Java. Lang. ClassNotFoundException: com. Mysema. Query. DML. UpdateClause

Time:09-18

The Error is: "weblogic. Management. DeploymentException: Java. Lang. ClassNotFoundException: com. Mysema. Query. DML. UpdateClause"
Weblogic. Management. DeploymentException: Java. Lang. ClassNotFoundException: com. Mysema. Query. DML. UpdateClause
The at weblogic. Application. Internal. BaseDeployment. ThrowAppException (BaseDeployment. Java: 132)
The at weblogic. Application. Internal. BaseDeployment. Prepare (BaseDeployment. Java: 244)
The at weblogic. Application. Internal. SingleModuleDeployment. Prepare (SingleModuleDeployment. Java: 52)
The at weblogic. Application. Internal. DeploymentStateChecker. Prepare (DeploymentStateChecker. Java: 158)
The at weblogic. Deploy. Internal. Targetserver. AppContainerInvoker. Prepare (AppContainerInvoker. Java: 65)
Truncated. See the log file for complete stacktrace
Under Caused By: Java. Lang. ClassNotFoundException: com. Mysema. Query. DML. UpdateClause
The at weblogic. Utils. Classloaders. GenericClassLoader. FindLocalClass (GenericClassLoader. Java: 1035)
The at weblogic. Utils. Classloaders. GenericClassLoader. FindClass (GenericClassLoader. Java: 996)
The at weblogic. Utils. Classloaders. ChangeAwareClassLoader. FindClass (ChangeAwareClassLoader. Java: 101)
The at weblogic. Utils. Classloaders. GenericClassLoader. DoFindClass (GenericClassLoader. Java: 617)
The at weblogic. Utils. Classloaders. GenericClassLoader. LoadClass (GenericClassLoader. Java: 547)
Truncated. See the log file for complete stacktrace




A great god, and the mistake how to solve ah, want to crazy

CodePudding user response:

Common under Caused by: Java. Lang. ClassNotFoundException abnormal reasons:

ClassNotFoundException belongs to checkException (check), generally when project start, the reasons for the problems summarized as:

1. Don't have the right to import the jar,

2. Project cited multiple versions of the jar, causing version conflict, due to the upgrade version, may be used by the method has been abandoned,

3. Due to the load the web system. The order of the XML file, automatic injection (using the spring annotations) is probably not the spring loaded into memory, the normal use of spring's autowrite, lead to can not find such kind,



Reminder: please check the project in the tomcat lib contains the jar,
  • Related