looks like if you have an ejb in that jar it gives this error .. not if its a plain jar file.
I had a similar problem and put ../lib/....... instead of simply lib/....... to work around.
This is about jboss 3.2.1
Even i have similar problem.
This is my directory structure
Beans in Beans.jar requires the other four jars.
I specified that dependency using Class-Path : Backend.jar, tsglt50.jar, tsgltc5.jar
with a new line after this line.
When i deploy the beans.jar, jboss says that Beans.jar deployed.
But when i tried to do a jndi lookup on the bean, it says NameNotFound. By trial and error i removed the Class-Path line in the manifest line and now i am able to find the bean using JNDI lookup.
Now when i try to use the bean after lookup, it is not able to find some of the classes needed by the beans in beans.jar as they are present in the other jar files.
I am interested to know where to place the other jars such that it is visible to Beans.jar in jboss 3.2.1
I appreciate anybody's response to my posting.