Community
Participate
Working Groups
We are currently caching the launch object inside of the Server class, but adopter do not have a way of refreshing this object. Without access to refresh the launch object there is cases where the call to server.getLaunch will return null when in fact there is a true valid launch object associated. The adopter reported this problem while doing testing with restart cases.
Created attachment 168179 [details] v1.0
* Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. Currently adopters do not have a way to refresh the launch object, when the launch object has gone stale. * Is there a work-around? If so, why do you believe the work-around is insufficient? No * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Ensuring that changes do not cause any regression, all server.core and server.ui JUnits were ran. * Give a brief technical overview. Who has reviewed this fix? The changes introduce a new API at the Server and ServerBehaviourDelegate. Adopter do not need to react, unless they want to make use of the new method. * What is the risk associated with this fix? medium to low
Changes committed to HEAD
released to HEAD
New Gerrit change created: https://git.eclipse.org/r/108951