Check if your package contains the ejb-jar.xml under a "META-INF" directory. Thats the condition that makes it a ejb-jar as against a regular jar.
ejb-jar.xml ist under META-INF together with jboss.xml. both generated and ok as far as I can estimate.
Are there probs with compressed jars in jboss?
Does the probs belong to java version?
shell I post the xml files?
Assuming that your ejb-jar.xml file is correct, my guess is that your META-INF directory is not in all caps.
The meta-inf dir is called: META-INF. See .jar (6k) in attachement.
Yep, looks capatilized doesn't it... It wasn't though. A fun trick that Windows plays on us...
Here is what I did...
1.) Just to make sure I dropped your JAR into my JBoss deploy directory--it deployed as a simple JAR file as you said.
2.) Un-JARed your JAR to C:\test
3.) Copied the files out of the META-INF directory (which did indeed look capatilized)
4.) Deleted the existing META-INF directory
5.) Created a new one making sure to name it in all caps.
6.) Copied all your files from the copy of your old META-INF directory into the new META-INF directory I just created.
7.) JARed up the new group of files
8.) Dropped it into my JBoss deploy directory and ran into a encoding error during the EJB deployment task. I didn't spen any time trouble shooting this because my goal was to poove it was the META-INF directory.
Thank you. I realized the "CAP" problem just the other day. I posted the solution accidently in the wrong thread:
http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t= was just a ugly windows prob.
kudos to you nphelps :-)
sven alias fortesqque