This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I'm trying to deploy an EAR file in JBOSS 5.1GA with "all" configuration and getting a DeploymentException with message "failed to initialize bean container" and "Null beannMetaData". JBOSS is not started.
I saw there is a similar post with the same exception : http://community.jboss.org/thread/65998?tstart=0#4267965.
I do not have any Jboss libraries inside the lib directory inside the xxx.ear file. I have only some libraries
that are needed for our custom application. The EJB's inside the ejb-jar.xml seems to get loaded/registered. But when the
SAR file is getting deployed, it throws exceptions.
Could somebody point me as to what could be wrong?
Thanks for the response. All the EJB's ejb-module.jar gets deployed and my problem seems to be only with the SAR file deployment.
The workaround in the JIRA bug report says to move ejb1.jar out of lib to the root of the ear
and list it in the application.xml. But I do not have any EJB's inside the "lib" directory.
I tried some options and still not able to get the SAR file deployed.
1. I added the SAR file deployment to the ear/META-INF/application.xml and removed the jboss-app.xml.
2. I removed the SAR file out of the EAR file and deployed it independently and got the same error
as mentioned above in my original post. The EJB's got deployed and the deployment failed because of the SAR file.
We have already had some issues with ClassPath processing with MANIFEST.MF files. So even if your jar is outside the .sar, it still is referenced via the MANIFEST.MF of the .sar. It's better to just get rid of the .sar and then place the bean deployment jar in the deploy folder. The EJB jar can then additionally contain the jboss-service.xml in it's META-INF folder with the following contents:
Joined: Sep 30, 2010
Getting rid of the SAR file and adding the jboss-service.xml to the META-INF directory of the ejb's jar file seems to deploy the services.