EAR with failed EJB deployment causes other EJB deployments in same EAR to fail ------------------------------------------------------------------------------- Key: JBAS-6915 URL: https://jira.jboss.org/jira/browse/JBAS-6915 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2, EJB3 Affects Versions: JBossAS-4.2.3.GA Reporter: Brian Dill Assignee: Alexey Loubyansky Fix For: JBossAS-Branch_4_2 When deploying an EAR with two EJB deployments inside it, if the first deployment fails other deployments in that EAR will not be deployed. If you use <module-order>strict</module-order> in your jboss-app.xml and force the failed deployment to be last, the other deployment will deploy successfully, essentially partially deploying the EAR. I've uploaded a test case that contains an EAR with two EJB deployments. Hello EJB will succeed, but Goodbye EJB is designed to fail. Switch the module ordering in application.xml to see both the described effects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira