My problem was solved when I used an older version of Java.
JRE 1.8.0_71 x86 -> TC did not list jp2launcher process in object browser
JRE 1.6.0_23, x64 -> TC did list javaw process and had nested client objects
jp2launcher replaces javaw in newer versions of Java and maybe TC has an issue with it. My app normally runs on an older version of Java so it wasn't a problem for me.
Hi,
> My problem was solved when I used an older version of Java.
Thank you for the update.
(It also might be related to the https://community.smartbear.com/t5/Desktop-Testing/Can-I-test-a-JNLP-app-that-does-not-run-in-a-browser/m-p/122060#M6609 thread)
However, this sounds strange because I definitely was able to work with the JNLP application started using both javaw and jp2launcher processes (though do not remember their exact versions)...
As a quick idea - In TestComplete Object Browser try to use toolbar buttons (on the left of the Object Browser's toolbar) to display not only the tested applications but also all user processes and, maybe, system processes as well. Does this make jp2 launcher process visible and a parent of your jnlp application ?
This issue is already fixed. Please ask support for patch.
