[jbosstools-issues] [JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim edited comment on JBIDE-22803 at 10/10/16 11:15 AM:
---------------------------------------------------------------------

[~jcantrill] [~bdshadow] I grok/agree that we should ideally not rely on versions to determine whether a feature is (not) present. But if a try/fallback is hacky I believe we should. In the specific case trying to watch projects and catching it feels hacky since it seems that we have to consider the timing and the repetition. To top this claim it looks like there's a bug in the server where we get an error even though the message that we get presented reports "OK, could watch project".  ([~bdshadow] you might want to supply the details?). Furthermore we need an alternative approach if projects are not watchable. Maybe polling and freshing projects?  
We could possibly do the version check in the client library (and not in JBT) preventing consumers from relying on versions. 
I still believe that offering access to the version still could be a nice feature, already if its just for display purposes.


was (Author: adietish):
[~jcantrill] [~bdshadow] I grok/agree that we should ideally not rely on versions to determine whether a feature is (not) present. But if a try/fallback is hacky I believe we should. In the specific case trying to watch projects and catching it feels hacky since it seems that we have to consider the timing and the repetition. To top this claim it looks like there's a bug in the server where we get an error even though the message that we get presented reports "OK, could watch project".  ([~bdshadow] you might want to supply the details?). Furthermore we need an alternative approach if projects are not watchable. 
We could possibly do it in the client library (and not in JBT) preventing consumers from relying on versions. 
I still believe that offering access to the version still could be a nice feature, already if its just for display purposes.

> Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22803
>                 URL: https://issues.jboss.org/browse/JBIDE-22803
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.1.AM2
>            Reporter: Jeff MAURY
>            Assignee: Dmitrii Bocharov
>              Labels: explorer, openshift, openshift_v3
>             Fix For: 4.4.2.AM2
>
>         Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png
>
>
> EXEC: create an Openshift project
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> ASSERT: wait for the pod to be available
> EXEC: delete the Openshit project
> EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists)
> EXEC: expand it
> EXEC: Create an application in this project (nodejs-example)
> EXEC: expand the nodejs-example node
> ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)