JBoss-5 Beta4 - Redeploy exploded EAR not supported?

[jaikiran]

I am using JBoss-5 Beta4 on my test setup with Sun Java 1.5 and Windows 2003 Operating System. I have a very simple EAR file which is deployed in exploded format. The deployment works fine without issues. However when i "touch" (change last modified time) the application.xml file as mentioned at http://wiki.jboss.org/wiki/RedeployAnApplicationWhenChangeAFileInAnExplodedDeploymentDirectory, the application is not re-deployed. There's no indication in the logs which suggests that the changes to application.xml has been noticed.

I do know there are issues with redeploying a zipped EAR on Windows and JBoss-5 Beta4 because of file locking. But is this problem, with redeploying the exploded EAR, also a known issue? If not, should i open a JIRA for tracking this?

[jaikiran]

For my exploded EAR application deployed at

D:/JBoss-4.2.2/jboss-4.2.2.GA/server/jaikiran/deploy/EJB3Persistence.ear/

in JBoss-4.2.x, the getWatchURL method on MainDeployer MBean used to return

file:/D:/JBoss-4.2.2/jboss-4.2.2.GA/server/jaikiran/deploy/EJB3Persistence.ear/META-INF/application.xml

and i do see code in 4.2.x which used to add the application.xml as the watch url.

However in 5.0 Beta-4, for my exploded EAR deployed at

D:/jboss-5.0.0.Beta4/server/jaikiran/deploy/ZEJB3Persistence.ear/

the getWatchURL on MainDeployer just returns

D:/jboss-5.0.0.Beta4/server/jaikiran/deploy/ZEJB3Persistence.ear/

Was it intentional to stop adding the application.xml as the watch url for an exploded EAR?

[jaikiran]

"jaikiran" wrote:
I am using JBoss-5 Beta4 on my test setup with Sun Java 1.5 and Windows 2003 Operating System. I have a very simple EAR file which is deployed in exploded format. The deployment works fine without issues. However when i "touch" (change last modified time) the application.xml file as mentioned at http://wiki.jboss.org/wiki/RedeployAnApplicationWhenChangeAFileInAnExplodedDeploymentDirectory, the application is not re-deployed. There's no indication in the logs which suggests that the changes to application.xml has been noticed.

Downloaded the just released JBoss-5.0 CR1. Works fine on this version.

The exploded EAR application is redeployed when the application.xml is "touched".