[
https://jira.jboss.org/jira/browse/JBAS-7976?page=com.atlassian.jira.plug...
]
Alessio Soldano commented on JBAS-7976:
---------------------------------------
Ales, I've done some tries. After having applied the patch, I get an exception during
boot because something's looking for the previous constructor of EARContentsDeployer.
Added that, simply delegating to the new one and ignoring the int parameter. With that
"fix", I'm able to boot the AS. I then tried deploying the ear archive I
used to reproduce the problem (it comes from tck) and I get (perhaps my change is causing
that?):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment
"jboss.ejb3:application=Hello,module=Hello_ejb,component=Hello,service=EjbEncFactory"
is missing the following dependencies:
Dependency "jboss.naming:application=Hello,component=Hello,module=Hello_ejb"
(should be in state "Installed", but is actually in state "** NOT FOUND
Depends on 'jboss.naming:application=Hello,component=Hello,module=Hello_ejb'
**")
Deployment
"jboss.j2ee:ear=Hello.ear,jar=Hello_ejb.jar,name=Hello,service=EJB3" is missing
the following dependencies:
Dependency
"jboss.ejb3:application=Hello,component=Hello,module=Hello_ejb,service=EjbEncFactory"
(should be in state "Installed", but is actually in state
"Described")
Deployment
"jboss.j2ee:ear=Hello.ear,jar=Hello_ejb.jar,name=Hello,service=EJB3_endpoint" is
missing the following dependencies:
Dependency
"jboss.j2ee:ear=Hello.ear,jar=Hello_ejb.jar,name=Hello,service=EJB3" (should be
in state "Installed", but is actually in state "Instantiated")
DEPLOYMENTS IN ERROR:
Deployment
"jboss.ejb3:application=Hello,component=Hello,module=Hello_ejb,service=EjbEncFactory"
is in error due to the following reason(s): Described
Deployment "jboss.naming:application=Hello,component=Hello,module=Hello_ejb"
is in error due to the following reason(s): ** NOT FOUND Depends on
'jboss.naming:application=Hello,component=Hello,module=Hello_ejb' **
Attaching the jboss-app.xml of the Hello.ear and the jboss.xml of the Hello_ejb.jar it
contains. I can send you the archive if you need that.
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: JBossAS-6.0.0.M2
Reporter: Alessio Soldano
Assignee: Ales Justin
Fix For: 6.0.0.CR1
Attachments: [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