[
https://issues.jboss.org/browse/JBIDE-10518?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-10518:
-------------------------------------
Unfortunately changing the error message to a warning is impossible. The API for
ServerEditorPart and ServerSection only has a getSaveStatus() and a setErrorMessage().
Support for warnings seems non-existant really. We can see below that the getSaveStatus()
only takes an OK status or an error. Warnings will be interpreted as errors.
/**
* Returns error or status messages that will be displayed when the
* server resource is saved. If there are any error messages, the
* user will be unable to save the editor.
*
* @return a status object with code <code>IStatus.OK</code> if this
* server can be saved, otherwise a status object indicating why
* it can't be
* @see #getManagedForm() Use forms UI based for errors via {@link
org.eclipse.ui.forms.IMessageManager}
* on the message form instead of this method
*/
public IStatus[] getSaveStatus() {
return new IStatus[] { Status.OK_STATUS };
}
ServerEditorSection has similar code in it, making warnings impossible.
I've begun looking into whether it'd be easy or hard to cram the
serverworkingcopy information in as a model for databindings, but, it really doesn't
look to be an easy task.
[Longstanding][UI] Add warning for port section unable to find
integer port
---------------------------------------------------------------------------
Key: JBIDE-10518
URL:
https://issues.jboss.org/browse/JBIDE-10518
Project: Tools (JBoss Tools)
Issue Type: Task
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
Longstanding issue: When a port fails to resolve, the server editor cannot be saved or
modified in any way. This should be switched to a warning, with the default substituted in
as the proper value.
Since this issue is longstanding, and may be affected by a UI redesign, it is being
separated from JBIDE-10513.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira