Community
Participate
Working Groups
Build Identifier: 4.2.0.v20120315-1300 We, the Jubula team, currently check the compatibility of testing 3.x applications / plugins with e4.2 + compatibility layer and noticed that some internal classes have changed which we require for UI automation. E.g. the method org.eclipse.ui.internal.PartPane.getToolBar() does no longer exist. Which is the correct approach to access this toolbar in an 3.x / e4.2 compatible way? This results in a) an exception (NoSuchMethod) being thrown in the e4 application when our remote control component (org.eclipse.jubula.rc.rcp) bundle is present. b) an even more severe problem: preventing Jubula from testing those components. Reproducible: Always
The view toolbar itself is not (and has never) been exposed via API. You can't get access to it (at least not legally). Other hacks that may or may not work: crawl the widget hierarchy from the shell to find it. It's fairly dynamic in nature, so there's a lot of looking at CTabFolder's controls to find it or its parent container. Find the Part's MToolBar, get its widget, and it's either the toolbar or a composite that contains the toolbar (renderer specific). Get the view site, the action bar, and then the IToolBarManager. If it's an instance of ToolBarManager you can try getControl(). The implementation of IToolBarManager can be swapped out at any time, although that's not planned for Juno (but I couldn't guarantee it). PW
Thanks for your quick reply and your hints. We will check our code. Thank you MM
(In reply to comment #1) > > Get the view site, the action bar, and then the IToolBarManager. If it's an > instance of ToolBarManager you can try getControl(). The implementation of > IToolBarManager can be swapped out at any time, although that's not planned for > Juno (but I couldn't guarantee it). I'll just note that this hack is the most likely to work in both 3.x and 4.x. The trick would be to request the toolbar every time you need it, as in 4.x it can get disposed and recreated. PW
