-
1. Re: EJBDeployer handling of MANIFEST.MF broken in 3.2.1?
sraj Jun 26, 2003 9:22 PM (in response to troypoppe)looks like if you have an ejb in that jar it gives this error .. not if its a plain jar file.
-
2. Re: EJBDeployer handling of MANIFEST.MF broken in 3.2.1?
gudmundsonsc Jul 10, 2003 1:39 PM (in response to troypoppe)I had a similar problem and put ../lib/....... instead of simply lib/....... to work around.
-
3. Re: EJBDeployer handling of MANIFEST.MF broken in 3.2.1?
kprindia Aug 22, 2003 2:43 PM (in response to troypoppe)This is about jboss 3.2.1
Even i have similar problem.
This is my directory structure
Trendium.ear
OB.jar
Backend.jar
tsglt50.jar
tsgltc5.jar
Beans.jar
--- META-INF
--- com/trendium/ejbs/*.java
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.
Thank you