Bug 487970 - Republish does not set Starting state
Summary: Republish does not set Starting state
Status: NEW
Alias: None
Product: CFT
Classification: ECD
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2016-02-17 17:28 EST by Nieraj Singh CLA
Modified: 2016-02-18 12:35 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nieraj Singh CLA 2016-02-17 17:28:56 EST 
When publishing a server that has modules that need to be republished via "Publish" in Servers view context menu, Starting state for the module is not set.

Starting state for module is set in all other cases of "publish" (i.e. "Update and Restart" and "Push") as well as both "Start" and "Restart", both from editor and context menu actions.
Comment 1 Nieraj Singh CLA 2016-02-18 12:35:26 EST 
It seem that the issue is that the Servers view module state does not get updated when invoking this at any time during the publish operation. It works in any other case (restart, drag/drop, push..), but not in publish. Calling this doesn't seem to update the Servers view:

server.setModuleState(getModules(), IServer.STATE_STARTING);

Also this is not a regression introduced with the updated way of calculating Started state for an application, or any of the Starting improvements:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=486214
https://bugs.eclipse.org/bugs/show_bug.cgi?id=486781
https://bugs.eclipse.org/bugs/show_bug.cgi?id=487909

The issue is also present 1.0.0.M2 and older CFT (prior to implementing fixes for the bugs above) that used the old version of computing start state and had the old "legacy" restart behaviour.