[
https://jira.jboss.org/jira/browse/JBAS-7976?page=com.atlassian.jira.plug...
]
Ales Justin commented on JBAS-7976:
-----------------------------------
// new parsed metadata
JBossAppMetaData parsed = unit.getAttachment(JBossAppMetaData.class);
if (metaData == null)
metaData = parsed;
else
metaData.merge(parsed, metaData); // TODO - what's override and/or original
here?
Looking at the code, I see that JBossAppMD's merge() doesn't do much.
I'll check on what can be done there.
jboss-app.xml is not parsed when no application.xml is provided
---------------------------------------------------------------
Key: JBAS-7976
URL:
https://jira.jboss.org/jira/browse/JBAS-7976
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: 6.0.0.M2
Reporter: Alessio Soldano
Assignee: Ales Justin
Fix For: 6.0.0.CR1
Attachments: [JBAS-7976]__#2.patch,
[JBAS-7976]__fix_JBossAppParsing_deployer_.patch
JBossAppParsingDeployers does not actually parse jboss-app.xml when no application.xml
descriptor is provided. In that case, the EARContentsDeployer creates a JBoss50AppMetaData
instance and attach that to the deployment unit. Later JBossAppParsingDeployer (actually
AbstractParsingDeployerWithOutput::createMetaData(DeploymentUnit unit, Set<String>
names, String suffix, String key)) finds the metadata are already there and returns
without doing the actual parse.
A consequence of this is that, for instance, a security domain declared in jboss-app.xml
is not picked up.
--
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