The Java classloader is studied, and it is found that there is no place to consider the classloader in practical work.

as far as I know, the applications of Java class loader mechanisms are mainly OSGI framework, Tomcat implementation, etc., but there is no need to implement custom loader scenarios at all.

do my colleagues have the same idea?

Apr.02,2021

well, yes, it is very difficult for ordinary staff to have the opportunity to use it, but be sure to understand what is the class loader , what is the active loading of classes , what is the passive loading of classes , what is the parent delegation mechanism , how to skip the parent delegate mechanism
if you have studied the driver loading of jdbc or the SPI mechanism of any application (mainly some classes and implementations under the security package), you will know that the judgment of the class loader is widely used, including skipping the parent delegate mechanism, but if you do not have the accumulation of relevant knowledge, It is very troublesome to understand


cute new: you can export executable jar packages using spring-boot-maven-plugin, which is so convenient and does not need to be equipped with classpath.
Old Bird: his jar package is different from other fatjar. It's amazing that it can directly contain other jar packages.
Boss: although such a jar package can be executed directly, adding such a jar package to classpath has no effect. Other Java programs can't read the classes, so what to do?

Menu