On 12/9/05, Dennis Byrne <[EMAIL PROTECTED]> wrote:
One thing to recall when debugging NoClassDefFoundError problems ... the class name listed in the exception message is *not* the one that is missing! That would cause a ClassNotFoundException instead. Rather, it means that one of the classes that the named class itself depends on (i.e. imports, or uses as a type in an instance variable or method signature) cannot be found. Or, that a dependency of one of those dependent classes cannot be found ...
The important point is to start looking at what the named class depends on, instead of looking for the named class itself.
Craig
This is not necessary. I would confirm that this IS in fact
a problem when putting the jar under lib. If so, you may
have better luck investigating the container.
One thing to recall when debugging NoClassDefFoundError problems ... the class name listed in the exception message is *not* the one that is missing! That would cause a ClassNotFoundException instead. Rather, it means that one of the classes that the named class itself depends on (i.e. imports, or uses as a type in an instance variable or method signature) cannot be found. Or, that a dependency of one of those dependent classes cannot be found ...
The important point is to start looking at what the named class depends on, instead of looking for the named class itself.
Craig
