[
https://issues.jboss.org/browse/AS7-1248?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-1248:
-----------------------------------
Note that section EE.8.5.2 of Java EE6 spec says:
{quote}
The deployment tool must first read the Java EE application deployment descriptor from the
application .ear file (META-INF/application.xml). If the deployment descriptor is present,
it fully specifies the modules included in the application.
{quote}
However, it would be good _not_ to impose this rule for JBoss specific .sar nested
deployments because there's no way we can specify a .sar as a module within the
application.xml
Presence of application.xml in .ear causes nested .sar deployment to
be skipped from deployment
-----------------------------------------------------------------------------------------------
Key: AS7-1248
URL:
https://issues.jboss.org/browse/AS7-1248
Project: Application Server 7
Issue Type: Enhancement
Components: EE
Affects Versions: 7.0.0.CR1
Reporter: jaikiran pai
Assignee: jaikiran pai
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira