cancel
Showing results for 
Search instead for 
Did you mean: 

Java access bridge JAB - inconsistent results with applet application

RobertLatherow
Level 3
We are trying to interact with a older java applet based web application.  Working with the JAB has given us very inconsistent results.  For example, we will pass a wait conditional on a java element, then fail on a 'click' action because the object doesn't exists.  Attempting the same code a second time may work fine, or it may not.  The Application modeler often never returns back at all and needs to be killed. Has anyone else seen this, or have any ideas for a solution? -RJ
1 REPLY 1

PSSupport
Staff
Staff
cant say why it doesnt work when it highlights, maybe the attributes change somehow and you would need to track that change to only the use min attritubtes which uniquely identify and dont change.  For long delays, how java apps/webpage spying works is that it creates a heirarchical structure of the elememtns and then searches through it. In case of java based applications this structure may be quite big, depending on how the application is built. So for any action first BP would search the element. I have seen this search take a long time in some cases. Problem is even if you add a wait for element with a certain timeout (say x secs). BP would first search for the element which may take y secs, then apply the timeout (x secs), so overall the time increases to x+y secs, which may be too long.  Always do an initial application assessment, and in case these issues are encountered, SA (or anyother spying which works), needs to be kept as an option.