- This topic has 3 replies, 2 voices, and was last updated 19 years, 4 months ago by
.
-
Posts
-
Spec:
Eclipse 3.1.0
MyEclipse Version: 3.9.310 Build id: 20050808-4.0-Milestone-3
Tomcat 5.5.9
Windows XP HomeWhat I’m doing…
I deply my exploded application..
start tomcat.
Go to the application’s web root through the browser and there’s no files.
I try and redeploy but it tells me that “The deployment is out of date due to the changes in the underlying project contents……”
I can’t remove the application while tomcat is running either as a popup comes up with the same errorPlease help!
EurigEurig:
1) Remove your deployment
2) Right click on the root of your project and do a Refresh
3) Select Project > Clean, and rebuild your project.
4) Recreate the deployment.Are you running any custom Ant scripts? This can cause this to happen.
I’ve now managed to get it to deploy but it’s still acting weird…
The deployed app seems to be updating when i make changes to a JSP for example. It also lets me reload successfully when I edit a file such as MessageBundle.properties or something.
But when I try and redeploy using “Manage Deployments” it gives me the “Deployment is out of date due to changes in the underlying project contents….” status. The application stops working from that moment, I can’t start the application or remove it until tomcat has stopped.
I guess this is something to do with Windows’s filesystem. What is the best way to develop and work on an application when this gets in the way? What are your workarounds?
The deployed app seems to be updating when i make changes to a JSP for example. It also lets me reload successfully when I edit a file such as MessageBundle.properties or something.
Correct. If you don’t want it to do this, use a packaged deployment instead.
But when I try and redeploy using “Manage Deployments” it gives me the “Deployment is out of date due to changes in the underlying project contents….” status. The application stops working from that moment, I can’t start the application or remove it until tomcat has stopped.
No surprises here. If you are using an exploded deployment, you shouldn’t need to keep opening the deployment dialog to redeploy, it’s done for you already. Also if you are trying to redeploy to a running instance of your app server, it won’t work due to file locks.
I guess this is something to do with Windows’s filesystem. What is the best way to develop and work on an application when this gets in the way? What are your workarounds?
You are actually exactly right, just use an exploded deployment, that’s the easiest. Then all your changes are immediately sync’ed with the server.
