Current location - Quotes Website - Signature design - How to solve the verification error
How to solve the verification error
Generally speaking, there are two common situations:

1. When sealed: true has been marked in the list. MF of a jar file, all classes of java package in this jar must come from this jar package, which is a security measure of JVM. With digital signature, it can prevent tampering, so Microsoft signed its SQLServer driver. For example, JRE's rt.jar is sealed, so if you create a java.lang.MyClass class to run, the JVM will refuse. Usually, if you use AOP based on dynamic proxy, such as Hibernate delayed loading or Spring AOP, it may be because the temporarily generated subclasses themselves are generated in memory, not from jar packages. At this time, if the jar package is sealed, it will not work. For example, the JDBC driver of Microsoft SQL Server is sealed, and the delayed loading using Hibernate will get an error, because the proxy class generated by Hibernate inherits a class in JDBC driver package, but this driver package is sealed, and the package name of the generated class will get an error in the jar of the driver name.

2. Maybe the class version is wrong. This error is that you said that the version of other class libraries referenced by your current class is different from the version used when compiling this class. For example, your class A uses a class in c_ 1.0.jar and compiles it on the server, but the only class on the server is c_ 1. 1.jar, and the version is the same as C _ 668.