[jbosstools-issues] [JBoss JIRA] (JBIDE-24802) Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-24802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454561#comment-13454561 ] 

Andre Dietisheim edited comment on JBIDE-24802 at 8/28/17 8:05 AM:
-------------------------------------------------------------------

The PR was merged by mistake, it still has issues.
As agreed with Rob, I'll PR to his PR so that [~rob.stryker] sees how to get things done via databinding (no way around it here, manual changes to the error state would get overriden by the databinding)


was (Author: adietish):
As agreed with Rob, I'll PR to his PR so that [~rob.stryker] sees how to get things done via databinding (no way around it here, manual changes to the error state would get overriden by the databinding)

> Connection wizard: Lots of unnecessary errors in Error Log when filling oc location, Finish enabled even if oc location empty
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-24802
>                 URL: https://issues.jboss.org/browse/JBIDE-24802
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.5.0.Final
>            Reporter: Radim Hopp
>            Assignee: Rob Stryker
>            Priority: Minor
>              Labels: connection_wizard, openshift_v3
>             Fix For: 4.5.1.AM2
>
>         Attachments: Spectacle.F10835.png
>
>
> On-the-fly validation of "oc location" field in ConnectionWizardPage puts lot of errors into error log. I think that the on the fly validation should not be so agressive.
> !Spectacle.F10835.png!
> And another thing: Is there any reason why Finish is enabled even when there is not valid value in oc location field?



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)