when modified customization dialog is closed by pushing or clicking on the OK button in test, "local" wsdl is marked as
modified, dialog itself is disposed, but nothing else. There's no information dialog regarding regeneration of the ws
implementation class (as a result of this there are some outstanding non-saved changes in "local" WSDL file). This also
very rarely (<3% cases) happens in manual testing
- use of RequestProcessor.getDefault().post(...) (CustomizationWSEditor.java:157) - considered as performance risk
because it is not guaranteed that posted Runnable will run anytime soon; should use non-default instance of
RequestProcessor or even better java.util.concurrent.ExecutorService (OTOH problem can be somwhere else since mentioned
Runnable from CustomizationWSEditor.java actually never runs in the test)
- something what should be called in EDT is being called somwhere else
- some lost events somewhere
Will look at this in NB 6.1
moving opened issues where TM != dev to TM=TBD
will try to find some solution for this...
Yes, this scenario is still quite unreliable and, sometimes, the web services node even disapears.