- This topic has 18 replies, 7 voices, and was last updated 19 years, 4 months ago by
.
-
Posts
-
A button that shuts down container (if running), redeploys last deployment and starts the appserver again would save me from A LOT of clicks during my work day. 🙂
Regards,
Anders,Anders,
We appologize for the shortcommings with the current model. We have some rather large changes for the entire app server/deployment model that we are trying to find the right time to implement; hang in there with us.It’s much faster to use the Tomcat Plugin and Tomcat Manager and run the app directly from the workspace and reload the context when appropriate, than to re-generate a WAR, undeploy the app and redeploy the new WAR.
I’d like to see this “model” in MyEclipse.
Guys if you use an exploded deployment there IS no redeployment, your changes are hotsynced with the server immediately, so there is no clicking of any buttons required at all…
for TomcatPlugin, you can only get one tomcat container configured at the same time, but you get the ability to use restart button. for MyEclipse, i can get different versions of tomcat configured and choose which one to start. This is important for me to work with, but with a restart button, it can save me a lot of time to press stop server and start server 🙂
The classes are hot-synced, but all the other static files cached by Tomcat (like ApplicationResources.properties) etc. are not.
Also, when the method signature of a class changes, the VM is unable to hot-sync it, requiring a restart.
So hot-syncing is generally better than restart, but restart is sometimes needed.
And sometimes you have to be sure to avoid headaches that the version running is the one you are looking at in Eclipse.
The classes are hot-synced, but all the other static files cached by Tomcat (like ApplicationResources.properties) etc. are not.
Also, when the method signature of a class changes, the VM is unable to hot-sync it, requiring a restart.
This is why God invented the Tomcat Manager, open it up in a browser and just keep it handy, so when you need something like this restarted, just hit “Restart Context” and that single context will restart in 2-5 seconds and just keep working.
Please see the Tomcat docs on how to set it up and use it (actually you just need to add a privaledged ‘manager’ role and account to tomcat-users.xml to use it.
maybe this can be automated on a per-project fashion ? eg. when updating a non-syncable resource, automatically restarting the context ?
It is definately possible, but not likely something we will add. Other IDEs offer tight integration with a single app server (usually Tomcat), while we offer relatively tight integration with almost every app server on the market (so you guys don’t need to write specialized Ant scripts to do all the work)… so when it comes to these very app-server-specific enhancements, we generally don’t go down that road because it automatically implies 20x the work (for all the other app servers).
Although, as with everything else, if enough people wanted it, we’d do it 🙂
The Tomcat plugin doesn’t “explode” the WAR inside Tomcat’s webapps/, it creates a .conf in tomcat/conf/Catalina/localhost/ pointing to the project’s dir.
If I understand correctly, MyEclipse’s exploded deployment copies files to tomcat/webapps/
Can I point MyEclipse to tje project’s dir as the deployment destination? I’m afraid it might overwrite something…
Can I point MyEclipse to tje project’s dir as the deployment destination?
Do not do this, if you so desperately want to use your dev folder as the launch folder, even though using an exploded deployment will do *the same thing* for you, please change it manually in your Tomcat setup and just point to your dev dir. Although again, this isn’t a) supported and b) you get the same behavior by using an exploded deployment.
The problem is that MyEclipse doesn’t always “notice” that I changed a file, so it doesn’t copy the file to the exploded destination.
But other than that, I think the Tomcat Plugin behaviour is more logical. What is the advantage of copying files from the dev folder to Tomcat’s webapps over pointing Tomcat directly to the dev folder?
