[jboss-jira] [JBoss JIRA] Closed: (JBAS-2600) URLDeploymentScanner fails to redeploy the unpacked WAR after refreshing its web.xml
[ http://jira.jboss.com/jira/browse/JBAS-2600?page=all ]
Dimitris Andreadis closed JBAS-2600.
------------------------------------
Fix Version/s: No Release
(was: JBossAS-4.0.5.CR1)
Resolution: Won't Fix
This is just the way it works: the URLs list can point to either some directory whose
content is to be scanned, or a packed module.
An upacked module would need to have a trailing slash '/' to indicate it should be
treated as a directory, but then the scanner literally thinks it's a directory and
scans its content, which is not what we want.
There would be many changes required to handle this special case, for which the workaround
is trivial, so it's doesn't worth the effort.
URLDeploymentScanner fails to redeploy the unpacked WAR after
refreshing its web.xml
------------------------------------------------------------------------------------
Key: JBAS-2600
URL: http://jira.jboss.com/jira/browse/JBAS-2600
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployment services
Affects Versions: JBossAS-4.0.3 SP1
Environment: JBoss 4.0.3 SP1, Windows XP, Java 1.5.0_04
Reporter: Amir Mistric
Assigned To: Dimitris Andreadis
Priority: Minor
Fix For: No Release
When specifying a location of an unpacked war directory to scan and deploy,
URLDeploymentScanner will not redeploy the web application after I change its web.xml
file.
The relevant setting in jboss-service.xml (URLDeploymentScanner MBean) is as following
---snip---
<attribute name="URLs">
deploy/,
file:///C:\projects\myapp.war
</attribute>
---snip---
Note, myapp.war is actually a subdirectory containing explored WAR application.
However, if I change the URL to include enire projects subdirectory then changing web.cml
does redeploy the application. Setting is as following:
---snip---
<attribute name="URLs">
deploy/,
file:///C:\projects\
</attribute>
---snip---
I may be wrong but changing the web.xml in either scenario should trigger application
redeployment.
--
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