[ https://issues.jboss.org/browse/AS7-1248?page=com.atlassian.jira.plugin.s... ] jaikiran pai updated AS7-1248: ------------------------------ Summary: Presence of application.xml in .ear causes nested .sar deployment to be skipped from deployment (was: Presence of application.xml in .ear causes nested .sar and .war deployments to be skipped from deployment) Issue Type: Enhancement (was: Bug) Description: If a .ear contains a application.xml as follows: {code:xml} <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" version="6"> </application> {code} and also packages nested .sar files within the .ear, then those nested deployments are skipped. Removing the application.xml "fixes" the issue. Since we allow .sar deployments to be picked up even in the absence of application.xml and since (JBoss specific) .sar deployments can't be mapped as a module in application.xml, it would be good to consider these nested .sar deployments, even in the presence of the application.xml. was: If a .ear contains a application.xml as follows: {code:xml} <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" version="6"> </application> {code} and also packages nested .sar (and .war) files within the .ear, then those nested deployments are skipped. Removing the application.xml "fixes" the issue. The nested deployment should be picked up even in the presence of the application.xml. Forum Reference: http://community.jboss.org/message/613784#613784 (was: http://community.jboss.org/message/613784#613784) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira