ClassLoader behaviour on 3.2.0

[frito]

Hi,

this is the situation: I have deployed an ear with an ejb.jar, ejb-client.jar and a dependency.jar in it. The ear and the ejb.jar use the loader-repository tag for obtaining an own LoaderRepository. The ejb.jar has set its Class-Path with the ejb-client.jar (even using the ejb-client-jar tag) , but NOT with the dependency.jar in its manifest.

and now the question:
on JBoss 3.2.0 (final) I am able to use classes out of my dependency.jar. Is this ok, even if the dependency.jar is not listed in the manifest Class-Path?
If it is, why should I use the manifest Class-Path?

Greetings,

Frito

[ytzel]

look into http://belnet.dl.sourceforge.net/sourceforge/jboss/ClassLoading.pdf
this

the loaderrepository will serve all stuff (classes,resources,...) which is deployed from your ear