1. Check the system environment variables from %path%. Is any external java installation path is pointed? If that so, comment and try

2. Check that jasmine.jar(QTP Java loader) in the test environment variable.

Hi, thanks. I figured out what it was, it looks like qtp 10 is incompatible with jre 1.6.35, which was what my local install was at. Or maybe a better way to say it is that, in my setup at least, it is compatible with 1.6.25. When it was working on Monday I had jre 1.6.25. It must have updated on me. I simply uninstalled .35 and reinstalled .25 and I am able to pick up the javawindow class. And hey it only took me a day and a half of hair pulling to figure it out! I guess the good part is that now I know QTP inside and out! lol

Thanks again your comment made me think of the jre version as being an issue.

FYI, I also had to set the jre 1.6.25 install directory into the path environment variable.

FYI, I also had to set the jre 1.6.25 install directory into the path environment variable.

Never mind Its not working again. Checked jre version and im still at 1.6.26 and my environment variables are set correctly. Was working great yesterday, go to test some new code and all I can see is the window class again. I am really starting to dislike QTP. it seems like I spend the first half of everyday fixing this java issue just to have it happen the next morning. Anyone have any Idea why this is happening?

Thanks

Never mind Its not working again. Checked jre version and im still at 1.6.26 and my environment variables are set correctly. Was working great yesterday, go to test some new code and all I can see is the window class again. I am really starting to dislike QTP. it seems like I spend the first half of everyday fixing this java issue just to have it happen the next morning. Anyone have any Idea why this is happening?

Thanks

Never mind Its not working again. Checked jre version and im still at 1.6.26 and my environment variables are set correctly. Was working great yesterday, go to test some new code and all I can see is the window class again. I am really starting to dislike QTP. it seems like I spend the first half of everyday fixing this java issue just to have it happen the next morning. Anyone have any Idea why this is happening?

Thanks

Interesting piece of info, its not all java apps. I have another java app and qtp can see the object in that just fine. So why would QTP be able to see java object is one app but not the other? I know QTP has the capability to see the objects because I get it working after messing around with stuff for half the day.

ok so uninstall jre 1.6.26, reinstall it it works fine? so now I have a temp fix for it so i can at least move forward but reinstalling java every morning is not a long term solution.

ok so uninstall jre 1.6.26, reinstall it it works fine? so now I have a temp fix for it so i can at least move forward but reinstalling java every morning is not a long term solution.

Just to make sure this was repeatable I shut down the computer and started back up, java app only seen as window class again. uninstall jre reinstall it and as long as I don't shutdown it sees javawindow class again. Anyone know if there is a hotfix for QTP 10 for this?

I don't know! This time without restarting the computer or shutting down, just closing the java app and starting the app again and QTP doesn't see javawindow class. I reinstall java...again. and still can't see it. Restart the computer and reinstall java... Still can't see it. Shut down, power up and reinstall java... Still can't see it.  Something has to be triggered the first time a java app is launched that messes with QTP java hooks... This is ridiculous...

Monday morning, same boat... Does it maybe have something to do with 64 bit windows and QTP10? or a combination of those and jre1.6.25? Tried it on another 32bit windows 7 desktop with the same results.... What really sucks is that I have the entire test coded but can't complete testing since I cant get QTP to see the application anymore, and testing with QTP is required for this project... This is so frustrating! I don't think I will ever take another project that requires QTP.

Monday morning, same boat... Does it maybe have something to do with 64 bit windows and QTP10? or a combination of those and jre1.6.25? Tried it on another 32bit windows 7 desktop with the same results.... What really sucks is that I have the entire test coded but can't complete testing since I cant get QTP to see the application anymore, and testing with QTP is required for this project... This is so frustrating! I don't think I will ever take another project that requires QTP.