- This topic has 5 replies, 3 voices, and was last updated 19 years, 11 months ago by
.
-
Posts
-
In the past I’ve used the Sysdeo plugin for Tomcat with Eclipse. But in starting on a new project I decided to go with MyEclipse. I’ve gone through the tutorial and gotten it working but there’s one little thing I miss from Sysdeo days. It used to place “Start Tomcat” and a “Stop Tomcat” buttons in the button bar (along with a Restart which I don’t miss). Using MyEclipse I have to go find the “Run/Stop MyEclipse Application Servers” pulldown and from that choose “Tomcat 5” and finally choose “Start” or “Stop”. This is an operation I repeat dozens of times a day. Is there a way to configure the button bar to stop and start an app server directly? Thanks.
Eclipse 3.1
MyEclipse 4.0M2
JDK 1.5
Windows XPThere isn’t a way to customize the button bar, however, if you use an exploded deployment your changes are hot-synced with the server and the need for constant restarting goes out the window.
Unfortunately that doesn’t help in this case. The web app creates a database using a Java DBMS (hsqldb) running in the same JVM. I usually hit it with a few queries, see how the database turned out, then want to tear down the DB and start over. This requires stopping and starting the JVM due to locks on the DB files.
But thanks anyway.
Sorry to jump in the middle of your thread but…
Changes to jsp’s are hot-synced but when ever I try modify a servlet (add method, modify methods signature) I get an error and have to manually stop and start Tomcat.
So I’m in agreement that a button for Stop and Start or better yet, Restart would be a good thing. Or is there a way to fix my servlet problem?
wseubert,
If you dismiss that warning, and then sit and watch your app server console, you should note after a few seconds that it reloads your context anyway. I usually turn off that warning as it is actually from the app server itself (when the shape of your class changes, the hot sync spec doesn’t support that, so it sends back an error to the eclipse debugger), but Tomcat has the “reloadable=true” setting for your contexts that will go ahead and reload anyway. Between the two of them, I think I actually reset my app server once or twice in a 6hr coding session.
