-
Enhancement
-
Resolution: Done
-
Major
-
4.3.0.Beta1
-
None
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.
- is cloned by
-
JBIDE-21085 Connection/application wizard: reconnects if you get back and forth to the connection page
- Closed
- is related to
-
JBIDE-19759 Application wizard: cannot launch v3 application wizard via File->New->OpenShift
- Closed
-
JBIDE-20596 Next button in the New OpenShift Application window is enabled only after clicking Use default server check box
- Closed
-
JBIDE-20978 Connection wizard: switching to <New Connection> resets token but form is still valid
- Closed
- relates to
-
JBIDE-19931 Cannot launch v3 import wizard via File->Import->OpenShift->Existing OpenShift Application
- Closed