[jbosstools-issues] [JBoss JIRA] (JBIDE-21084) Connection/application wizard: reconnects if you get back and forth to the connection page

Marián Labuda (JIRA) issues at jboss.org
Thu Nov 26 08:11:00 EST 2015


     [ https://issues.jboss.org/browse/JBIDE-21084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marián Labuda closed JBIDE-21084.
---------------------------------


Verified in nightly 4.3.1.Beta1 build with OpenShift plug-ins version 3.1.0.Beta1-v20151123-1937-B86.

> Connection/application wizard: reconnects if you get back and forth to the connection page
> ------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-21084
>                 URL: https://issues.jboss.org/browse/JBIDE-21084
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>             Fix For: 4.3.1.Beta1
>
>
> What makes this necessary is the internal behaviour of the connection page being used when application- or import-wizard are launched from central or file-menu. It there is a delegating wizard page which invokes either v2 or v3 wizard based on the server type that the user is choosing. Behind the scenes I see the conn wizard connecting several times when launched from central/file-menu. The delegating wizard page needs to connect in the WizardPage#getNextPage(), a method that is also used in PageChangingListener(s)  which it's using to determine the page change direction (forward or backward).
> how to reproduce:
> # EXEC: launch application wizard
> # ASSERT: connection page shows up
> # EXEC: select an existing or create a new connection
> # EXEC: get to the next page
> # EXEC: get back to the connection page and hit "Next" again
> Result:
> You see the progress bar coming up and getting to the 2nd page again after some delay caused by the the wizard re-connecting.



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



More information about the jbosstools-issues mailing list