Disable NameMapping Cache?
Hi, I know that the objects used by namemapping are "cached" for performance purposes. And because of this caching, everytime an object property is changed, RefreshMappingInfo must be called on...
Forum Discussion
Hi Alex,
Apologies for not clarifying. I'd written another post about the problem, but it didn't seem like anyone knew the answer / maybe it didn't get noticed - so I tried to think of other ways to solve it. Any help would be appreciated.
Basically, in our Swing app, some of our JDialog code is written a bit poorly, as in, some of the JDialogs are not disposed of properly. For example, when you open a dialog in the app, then close it, a new dialog instance will be created when you open the dialog again, and the old instance will remain invisible in the background.
This is causing trouble with namemapping because that old, invisible, instance is cached, and the only way I know to get the new, visible, instance is by calling RefreshMappingInfo on the mapped object. I am currently using AWTComponentName, which is set in the code and very static, and the Visible property to identify components.
This is doable, but a bit tedious, as we are trying to keep things as simple as possible for QA (keeping to keyword tests, straightforward test recording, as little 'hacking' as possible, etc.). Clearly, another option is to clean up those dialogs, but I was wondering if there were other possible solutions, if only to have a wider selection of options.
Thanks for any help.
Apologies for not clarifying. I'd written another post about the problem, but it didn't seem like anyone knew the answer / maybe it didn't get noticed - so I tried to think of other ways to solve it. Any help would be appreciated.
Basically, in our Swing app, some of our JDialog code is written a bit poorly, as in, some of the JDialogs are not disposed of properly. For example, when you open a dialog in the app, then close it, a new dialog instance will be created when you open the dialog again, and the old instance will remain invisible in the background.
This is causing trouble with namemapping because that old, invisible, instance is cached, and the only way I know to get the new, visible, instance is by calling RefreshMappingInfo on the mapped object. I am currently using AWTComponentName, which is set in the code and very static, and the Visible property to identify components.
This is doable, but a bit tedious, as we are trying to keep things as simple as possible for QA (keeping to keyword tests, straightforward test recording, as little 'hacking' as possible, etc.). Clearly, another option is to clean up those dialogs, but I was wondering if there were other possible solutions, if only to have a wider selection of options.
Thanks for any help.