Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am learning ClassLoader in Java, then I want to know, why JVM has many classloaders, why not only one? The one first load <Java_Runtime_Home>/lib, then load <Java_Runtime_Home>/lib/ext, and last load classpath.
If you have custom classloader, the system’s first.
Somebody can tell me why JVM has many classloaders?
One very useful application is to be able to deploy several web applications into a single Java EE server.
Each application might use different versions of the same libraries, and must thus have a different classloader from the others in order to be able to have different versions of the same classes in a single JVM.