[
http://jira.jboss.com/jira/browse/JBAS-4763?page=all ]
Brian Stansberry closed JBAS-4763.
----------------------------------
Resolution: Done
I'm closing this, as the core issue of a war with a missing dependency being complete
deployed is resolved. You can no longer deploy such a war and successfully access
it's resources. And you can count on the dependency being respected if its not
missing. The discussion on the forum of what sort of further failure action the deployers
should talk when a dependency is missing is really a separate issue.
Depends element in jboss-web.xml ignored
----------------------------------------
Key: JBAS-4763
URL:
http://jira.jboss.com/jira/browse/JBAS-4763
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.Beta4
Adding a depends element to jboss-web.xml seems to have no effect. Simplest way to
confirm this is to add a jboss-web.xml with the following to deploy/ROOT.war/WEB-INF and
start JBoss:
<!DOCTYPE jboss-web PUBLIC
"-//JBoss//DTD Web Application 5.0//EN"
"http://www.jboss.org/j2ee/dtd/jboss-web_5_0.dtd">
<jboss-web>
<depends>jboss:service=NonExistent</depends>
</jboss-web>
The ROOT.war deploys without issue even though the dependency is unresolved.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira