The JAR file layout you quote appears to show AAAException.class in mycomp/ejb, not
mycomp/ejb/myejb. Perhaps this is the problem?
a
href=http://www.jboss.org/index.html?module=bbop=viewtopicp=3827021#3827021;View
the original post/a
a
First guess, it is not the exception class which is not found, but a class it uses or
extends (could even be an uninitialised member variable).
Joachim
a
href=http://www.jboss.org/index.html?module=bbop=viewtopicp=3827022#3827022;View
the original post/a
a
Hello!
Thanx for the reply and help.
I like JBoss but I don't like the lack of docs for it... :)
triathlon98, thank you.
You guess was JUST right. AAAException was extending another exception which I'm
bundling in a seperate jar file. I copied that jar to the /deploy folder, then tried
to
anonymous wrote :
| It was a very simple mistake, but I wonder.. how come the stack trace for the
error did not contain any hint about the root class which is missing??? Guess JBoss
needs to include the relevant errors in there, no?? :)
|
Nothing JBoss specific, this is just how Java
Yes, NoClassDefFoundError is thrown to tell you that you are missing a class, and I
don't know where to load it from...
In my case:
AAAException extends BaseException
BaseException was not included. OK.
I am just wondering here, why can't the ClassLoader say: I cannot find class
definition
Hey Zeron, I've been there done that. I spent a whole day on this one and related
errors, and found the best solution was to tidy up my development environment so that
the class path available when I compile is exactly the same or more restricted than
the class path used by JBoss's class
