Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332708 - Move to non-internal API for finding an IWorkbenchPart's corresponding Control
Summary: Move to non-internal API for finding an IWorkbenchPart's corresponding Control
Status: CLOSED WONTFIX
Alias: None
Product: Jubula
Classification: Technology
Component: RC (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-16 04:40 EST by Zeb Ford-Reitz CLA
Modified: 2012-02-23 02:46 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Zeb Ford-Reitz CLA 2010-12-16 04:40:31 EST 
The RCP RC plug-in makes use of the following internal API:
 * org.eclipse.ui.internal.WorkbenchPartReference
  * getPane()
 * org.eclipse.ui.internal.PartPane
  * getToolBar()
  * getControl()

These classes and methods are used in order to figure out which Control corresponds to an IWorkbenchPart, so that the Control can be assigned a name based on the ID of the Part. This functionality must be maintained, but it would be nice (less risky) not to use internal API in order to accomplish it.
Comment 1 Achim Loerke CLA 2011-03-07 03:17:07 EST 
This is for documentation purposes only. There is no way to implement this functions without using those APIs.
Comment 2 Alexandra Schladebeck CLA 2012-02-23 02:46:13 EST 
See comment from Achim.