- This topic has 9 replies, 6 voices, and was last updated 20 years, 7 months ago by
.
-
Posts
-
Right now, every time I need to stop/start my Resin server, I need to deal w/hovering over the start/stop toolbar button, waiting for the resin flyout menu, then moving over to select start or stop. How about 3 easy to hit buttons, right on the toolbar: stop, start, restart.
Sounds small, but this is done many many many times a day.
Thanks.
-Scott
I agree, almost…
Maybe it would be better to have two buttons: a start/stop button and a restart button. The start/stop button should be a start button whenever the server is not running, and a stop button when the server is running.
Of course, the restart button would only be enables whenever the server is running.
On the other hand, it would be even better if there was no start button at all but ‘simply’ a launch configuration that would start up the server and fire up a browser with some configured inititial address. I remember working this way with applets in VS6.
Guys you are exactly right, we have been tossing around ideas and drafts internally but your feedback helps us narrow the situation down. I’ll pass the feedback on.
The issue has been that designing UI controls for combinations of the 22 connectors that we support led us to the general server drop-down toolbar control. In our EASIE plugin days we distributed individual appserver connector plugins with their own toolbar start/stop controls. The issue there was toolbar space mgmt when multiple servers control buttons were added. For 2.8 we plan to reintroduce that capabilty. Thus you will be able to customize the toolbar with start/stop controls for the server(s) of your choice in addition to or as a replacement for the current server drop-down control.
What about a “process kill” button? While debugging/testing, I never “stop” the Tomcat process, I’m just killing it. It’s faster and I want anyway to get rid of the saved session info.
Better even: option in the EE server settings if the Stop/Restart-buttons should do “Stop” or “Kill” ==> more people happy with same number of buttons in the toolbar!
—
VictorI haven’t heard anyone discussing this anymore, but what about my suggestion to launch a previously configured browser upon hitting start server?
It sounds like a minor thing, but during some debug sessions I do this all the time:
1) Click ‘face with running man’, select server, select start
2) launch or switch to browser
3) type in web addressCompare this to starting up a regular app:
1) Click ‘bug’Also,
Starting the server might pop-up a dialog stating that there are un-saved (and therefore undeployed) changes in the editor(s).
