[schuer]

hi,

That would be nice if the Run/Stop server button held the latest server started. In practice, I think you only use one app server. So we would not have to click (or browse the arrows) 3 times to get our app server started.

So the behavior would be like the Run button (to run java main class) of Eclipse.

That would be a nice feature, because we click a lot on this button.

Thanks.

[rwells@emcien.com]

I’ve found this to be annoying as well. I’d like to just click the button once.

To handle the start/stop aspects of this might be handled nicely by making the button a toggle, pressed in when the server is running or out when the server is not running. Though I’m not sure if toggles are supported on eclipse toolbars.

[Riyad Kalla]

Guys sorry you are running into this annoyance, the whole application server launch model is one of those legacy issues that we are very aware of its shortcommings, but instead of spending resources trying ot make it slightly better piece by piece, we want to rip it out and replace it but the change is far from small… it will happen but there is no ETA as of yet, hang in there, we’ll make it better I promise.

[nat101]

For that matter, please have a 1-button ‘deploy’ button. For app servers (most of them) that require auto deployment to be in wars/ears, there are too many steps to just re-deploy. (woa! How spoiled ME has made me!!!) Just have a button that deploys current project to default/current app server.

-nat

[rwells@emcien.com]

And to add to our one button panacea request, after the one button deploys the project to the default app server it should launch the default browser and load the root of the web app context. This would allow me to “Run” my web app with a single buttun press.

you’ll have that out next week right 🙂

[Riyad Kalla]

you’ll have that out next week right 🙂

Not quite, but I will file this… I can’t promise this will happen though.

This is like someone with gangrene about to loose a leg asking you to go to the store to get the best nail polish you can find and paint their toes for them… you are pretty hard pressed to spend any time since you just need to cut their leg off tommorow anyway.

That’s a bit extreme, but you catch my drift.

[Paul Kaiser]

@support-rkalla wrote:

This is like someone with gangrene about to loose a leg asking you to go to the store to get the best nail polish you can find and paint their toes for them… you are pretty hard pressed to spend any time since you just need to cut their leg off tommorow anyway.

That’s a bit extreme, but you catch my drift.

So I guess scrubbing the callouses off the heel is out, too? 😉

[Riyad Kalla]

Hhaha, its out just for right now… let us get 3.8.3 out the door and get 3.9 squared away and some more improvements will make it in there.

If its any consolation all these enhancements you guys are asking for is stuff I want too, so you have someone ‘on the inside’ that is pushing for their addition as well, but not having the development effort of them preempt adding major new functionality.

[arjan.tijms]

@rwells@emcien.com wrote:

And to add to our one button panacea request, after the one button deploys the project to the default app server it should launch the default browser and load the root of the web app context. This would allow me to “Run” my web app with a single buttun press.

*smile* I requested the exact same feature about 3/4 year ago:

https://www.genuitec.com/forums/topic/start-stop-servers-should-be-broken-into-2-separate-buttons/&highlight=

I 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 address

Compare this to starting up a regular app:
1) Click ‘bug’

😉

[nat101]

After using ME more heavily, my ‘one button DEPLOY’ request does not seem far-fetched at all.
(Since I now have many projects, it adds many more clicks to get deployed.)
As a matter of fact, your designers are obviously in agreement on this, since they did include hot-deployment for UNpackaged files. Now, just because my appserver only allows wars and ears to be deployed does not mean that I don’t want to hot-deploy! Ok, you say that to automatically jar up so many files on every change is silly. Agreed. But at least let me one-button deploy when I want!

As far as launching the browser, please make it optional, via a checkbox. I certainly don’t want that, since I have my multi-tabbed browser always loaded, and I simply hit reload after re-deployment.

[Unrelated]Also very important, is for Eclipse to warn if I close Eclipse and the Appserver process is running. And related to this, or due to this, I would prefer to start my Appserver externally (in debug mode), but alas, ME cannot attach its console to it.

ok. ok. I’ll shut up and wait….
….
….
….

HOW LONG should I wait???
🙂
-nat

[Riyad Kalla]

nat,
1) There is no argument over one-button-deploy, its a good idea; as I mentioned we are busy with bigger/better improvements and we might need to suffer without one-button deploy for a little longer.

2) Opening the browser or having a one-button-run like NetBeans is a good idea and is filed, additionally quick-launching the browser is cool.

3) Externally running servers: this is a new addition to 3.8.3 😉

HOW LONG) #3 will be comming in 2 weeks with 3.8.3, #2 I don’t have an ETA for this, #1 No ETA either.

[nat101]

I’ll take what I get. 🙂

On #3, external servers, can those servers be anywhere on the network, or only on the same machine?

Thanks,
nat

[Riyad Kalla]

IIRC anywhere

[Author]

Posts