from the similar Q ava-securityexception-signer-information-does-not-match. I'm got this:
This happens when classes belonging to the same package are loaded from different JAR files, and those JAR files have signatures signed with different certificates - or, perhaps more often, at least one is signed and one or more others are not (which includes classes loaded from directories since those AFAIK cannot be signed).
BUT I get more Q about this:
- why the second time that jvm load the same class not from cache(if there are, but if without cache, then why);
- why when the second time that jvm load the same class, the jvm load order is not the same as the first time; in may opinion, if the order is same as the first time, then jvm should load the same class from the same jar as the first time.
