when LoadClass cannot load a class, it reports a ClassNotFoundException. Which identifies the problem, but not any causes.
Here is the proposed fallback
1. Look for the class as a resource; this identifies other classloading issues. Indicate that the .class is found, even though the class will not load.
2. Look for the parent package. This identifies bad packaging problems. Question is, can it be done?
3. Include a list of JAR files in the exception
Description
when LoadClass cannot load a class, it reports a ClassNotFoundException. Which identifies the problem, but not any causes.
Here is the proposed fallback
1. Look for the class as a resource; this identifies other classloading issues. Indicate that the .class is found, even though the class will not load.
2. Look for the parent package. This identifies bad packaging problems. Question is, can it be done?
3. Include a list of JAR files in the exception
Improvement
Resolved
Major
LoadClass to provide better diagnostics when a class is not found
