Re: [abbot-users] Query regarding Abbot.

[Timothy W. <tw...@us...>]

The best way to avoid recording issues is to give a unique name to  
every component.

Some of the oracle folks posted a patch recently that improves  
capture of component references.  That may or may not help your  
situation.

Sometimes these cases involve components that truly can't be  
distinguished, but usually in that case the recording will abort.

There are some issues with stuff that has JOptionPane.getRootFrame()  
as an ancestor and multiple app contexts.

It might help to dump your existing hierarchy (export hierarchy in  
the costello editor) and compare against the recorded script.  Also  
pay attention to whether it makes a difference whether it's the first  
or a subsequent run of the application.  Since the editor does  
everything from the same VM, it's important that components that are  
no longer in use are properly filtered (if they cannot be GC'd).

On Dec 27, 2006, at 1:16 PM, Maitri wrote:

> Hi Tim,
> Hope you're doing great.
> We have been using abbot for past 2-3 months and sometime we run  
> into strange issues. One of those is -abbot can't run a script it  
> recorded a moment ago. It faces issues in resolving the reference  
> and for given reference it can't distinguish between 2-3  
> components. If that's the problem, then how abbot records it and  
> what can be done to avoid such cases? Does it have to do the way a  
> GUI has been coded?
> Please help.
>
> Thanks
> -Maitri

Timothy Wall
http://abbot.sf.net