Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 348694

Summary:

It should be possible to add a progress dialog for potentially long running operations like start and stop

Product:

[WebTools] WTP ServerTools

Reporter:

Alexander Silgidjian <alexander.silgidjian>

Component:

wst.server

Assignee:

wst.server <wst.server-inbox>

Status:

RESOLVED WONTFIX

QA Contact:

Elson Yuen <eyuen7>

Severity:

enhancement

Priority:

CC:

eyuen7, kaloyan

Version:

unspecified

Target Milestone:

Future

Hardware:

OS:

Windows 7

Whiteboard:

plan_draft_331

Attachments:

Description	Flags
Itroduce a progress bar during server start.	none

Description Alexander Silgidjian

2011-06-08 05:51:44 EDT

Build Identifier:  3.3.0.v201102200555

When Server Adapter framework is used on some heavyweight servers and these servers have some lengthy start and stop operations it should be possible to alert the user with a user progress monitor. With the current implementation, start and stop operations are run without user progress dialog.

It should be possible to add a progress dialog for start and stop operations. This dialog should be easily moved to the background by the user.



Reproducible: Always

Comment 1 Alexandrina Ivanova

2011-06-30 09:13:36 EDT

Created attachment 198907 [details]
Itroduce a progress bar during server start.

Comment 2 Elson Yuen

2012-04-18 11:03:14 EDT

Given that the server start job can be kicked off via API, the operation may or may not be initiated directly by the user.  It can cause the flow of other scenarios to look strange, e.g. in case someone calls the API in a wizard or their own dialog to start the server, the progress should be keep track by the wizard progress or existing dialog progress instead of showing another progress dialog.  Besides, the user can see the server start is still progressing on the bottom right of the window that shows the job progress. I think we should leave the existing behaviour as is.

IMHO, if the server always expect to take a long time, it is probably better to put it to the background anyway; otherwise, the user needs to click it to run on background every single time that they start the server.