[jbosstools-issues] [JBoss JIRA] (JBIDE-12902) Project runtime pref page modifies original model without call to performOK or performApply

[ https://issues.jboss.org/browse/JBIDE-12902?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-12902. --------------------------------- Fix Version/s: 4.0.0.Beta2 (was: 4.0.0.CR1) Resolution: Done The attached patchb is obviously empty. I made only the changes max suggested in his last comment to the text of the message box. Use cases for QE: 1) Open runtime pref page, add new runtime path, then: a) assert new runtime is added b) press cancel c) re-open pref page, assert: 1) runtime is still added in server view, but 2) runtime PATH is not on the pref page 2) create one runtime path, press ok, re-open runtime pref page, see one runtime path. click "remove", click "cancel", re-open pref page, assert path still there 3) create one runtime path, press ok, re-open runtime pref page, see one runtime path. click "remove", click hyperlink next to JBossAS, assert message box appears. a) If press no, assert dialog goes away, nothing happens b) If press yes, assert preference dialog closes, re-opens on wtp runtime preference page Ensure that all the flashing and re-opening of the preference page dialog has stopped except in example 3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira