[jbosstools-issues] [JBoss JIRA] (JBIDE-20377) [origin_intservice_59]Port forwarding info disappeared after refreshing pods

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim commented on JBIDE-20377:
------------------------------------------

[~jcantrill] the good news in this is that this explains some of the "fishy" behaviours we talked about yesterday.

The underlying prob imho is that we have a client-side state (local port forwarding process) that we mix with server-side states (server resource).
Following this logic I would think that client side state should be handled in the client/Eclipse (ex. via singletons), not in the resource objects (IPod).
Agree?
Here's an idea that maybe explains it better:
PortForwardProcessRegistry with a #get(IPod) -> returns PortForwardProcess that holds a reference to the uid of the pod? 
Pod could create and return these, leaving the caller the responsability to not create those multiple times.

> [origin_intservice_59]Port forwarding info disappeared after refreshing pods
> ----------------------------------------------------------------------------
>
>                 Key: JBIDE-20377
>                 URL: https://issues.jboss.org/browse/JBIDE-20377
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.0.Beta2, 4.3.0.CR1
>            Reporter: Yue Wang
>              Labels: application_wizard, openshift_v3
>
> Start a port forwarding, you can find port forwarding status 'Started' in 'Application port forwarding' window, then you refresh pod and go to 'Application port forwarding' window again,  port forwarding status disappeared.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)