[Martin_Kersten]

I am running in the following problem:

I created a ear project and attached two subprojects (ejb and web) to it. I can deploy it in exploded version without fail but after hitting redeploy I get an error stating that the deployment fails and i should shut down JBoss and remove it manually.

Investigating the deployment every file is missing except the lib included in WEB-INF/lib. Therefore it is no wonder, JBoss kept complaining about a missing application.xml file.

And what me bugges even more is, if I am redeploying it in packaged mode it MyEclipse does it duty everytime and everything works well. So the question is, what am I doing wrong?

Thanks

[support-michael]

I doubt that you are doing anything wrong but rather it is more likely that JBoss is locking a jar or directory in its deployment area that prevents MyEclipse redeployment logic from deleting/recopying that file or directory. We have a Reload feature queued up in development that will resolve most of the file locking problems experienced during redeployment.

Here is what we do (while waiting for the reload feature for exploded deployments).

JBoss will reload an exploded application if you modify the timestamp of its deployment descriptor. For your enterprise apps this is the application.xml file. So open application.xml in MyEclipse and add/remove a space character. Then save the file. The MyEclipse sync-on-demand deployer will then replace your deployed app’s application.xml file. This should cause Jboss to reload your application without the heavy redeployment operation.

Michael
MyEclipse Support

[Author]

Posts