| Summary: | Unable to refresh the launch object used for the start server | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP ServerTools | Reporter: | Angel Vera <arvera> | ||||
| Component: | wst.server | Assignee: | Angel Vera <arvera> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Angel Vera <arvera> | ||||
| Severity: | major | ||||||
| Priority: | P3 | Flags: | arvera:
pmc_approved?
(david_williams) arvera: pmc_approved? (raghunathan.srinivasan) arvera: pmc_approved? (naci.dai) deboer: pmc_approved+ arvera: pmc_approved? (neil.hauge) arvera: pmc_approved? (kaloyan) |
||||
| Version: | 3.2 | ||||||
| Target Milestone: | 3.2 RC1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| See Also: | https://git.eclipse.org/r/108951 | ||||||
| Whiteboard: | PMC_approved | ||||||
| Attachments: |
|
||||||
|
Description
Angel Vera
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 |