Please see post http://forums.fanfaresoftware.com/t5/GUI-Testing-Web-Java-Swing-etc/How-to-test-Swing-application-launched-via-Java-Web-Start-JNLP/m-p/5699:
PreetS, 03-08-2010 03:02 PM
"The problem in kn_reddy's scenario was that the initial java process that is launched, ends up launching a secondary process and closes itself. iTest can not deal with that at the moment. It sees that process it has launched has exited, so iTest would close the swing session. "
I am seeing the same behavior with my java webstart client. Is there a solution to this problem yet?
I am currently running itest 3.4.1, but plan to upgrade to 4.1 soon.
Running java 6 SE, version 6, update 23, build 1.6.0_23-b05.