I'm running into a general problem with setting editor dialog subclasses of SettingsEditor opened via my plugin. The problem is 2-fold and both problems are related:
Scenario: open up a new dialog powered by the SettingsEditor class. DO NOT touch any ui component that modifies the configuration/settings backed by the editor. Click 'Ok' to save the dialog.
1) I see no way to perform validation on the dialog because SettingsEditor#applyEditorTo is not invoked.
2) The configuration in the dialog is not saved. Again, this because the applyEditorTo() method is not invoked. See DeployToServerSettingsEditor#applyEditorTo for an example of how the configuration would be set. This leads to downstream NPEs due to the null configuration.
So the basic question is how can these editors be marked "dirty" or "modified" immediately upon loading so that validation can be performed upon saving (and the configuration saved)?