ONJava.com -- The Independent Source for Enterprise Java
oreilly.comSafari Books Online.Conferences.

advertisement

AddThis Social Bookmark Button
Article:
  10 Reasons We Need Java 3.0
Subject:   ClassLoader problem
Date:   2002-08-28 14:10:57
From:   bjsyd70
Response to: ClassLoader problem

I wonder how much of this could be resolved by just improving the diagnostic message, so you could instantly see what was going on.


Is the solution difficult to determine, or is the problem difficult to diagnose?


Classes which use Class.forName often can not be shared by multiple .war files.


What about using a 'getCaller' method?


i.e. getCaller().getClass().getClass(name);


The runtime information must be there so the exception stack trace works.