Community
Participate
Working Groups
Created attachment 236014 [details] StackTrace ================= Scenario ================= I'm using a pure e4 part in an Eclipse 3.x perspective. When i open the part via "Show in (<ViewName>)" via the quick access then a ClassCastException occurs (see attachment for the stacktrace). The code line where the exception occurs is the following (in org.eclipse.ui.internal.WorkbenchPage.busyShowView): legacyWindow.firePerspectiveChanged(this, getPerspective(), CHANGE_VIEW_SHOW); } return compatibilityView.getView(); } part = showPart(mode, part); EXCEPTION OCCURS IN THIS LINE OF CODE ============================================================================ CompatibilityView compatibilityView = (CompatibilityView) part.getObject(); ============================================================================ if (compatibilityView != null) { IWorkbenchPartReference ref = compatibilityView.getReference(); legacyWindow.firePerspectiveChanged(this, getPerspective(), ref, CHANGE_VIEW_SHOW); legacyWindow.firePerspectiveChanged(this, getPerspective(), CHANGE_VIEW_SHOW); } return compatibilityView.getView(); } I considered, that the fix could be that at this location an instanceof-check is performed, but I really don't know if this is the correct fix. Also it's very strange, that the ClassCastException occurs, but the view is opened and except of the ClassCast everything is fine.
Could you please prepare simple plugin that exposes this issue? Daniel
A pure Eclipse4 view in the Workbench is not yet supported. I'll leave this open so it can be addressed. PW
Hi Paul, thank you for the pretty fast response. Is there any way so that I can fix this issue (or probably avoid the occurence of the exception) in our own code temporarily? For example override some method or override the command which does the "Show In" action? Thanks for your help! :)
(In reply to Alexander Fichtinger from comment #3) > Hi Paul, > > thank you for the pretty fast response. > Is there any way so that I can fix this issue (or probably avoid the > occurence of the exception) in our own code temporarily? You wouldn't be able to use your Eclipse4 view with the Show View command, you'd have to write your own command and handler for your view and add it to the model so it renders yourself. PW
Eric, related to your work with hosting Eclipse4 parts. PW
Voted for this bug because it causes some problems within our new product: For example, it causes standard eclipse keyboard shortcuts like Ctrl+F7, Ctrl+F10, F12, etc, not to work within our views.
Yesterday we wanted to fix the ClassCastException which I mentioned in the bug description. Then we discovered that it does not occur anymore (with Luna Milestone 4). But we still have the problem that the shortcuts like Ctrl+F7, Ctrl+F10, F12, Ctrl+M etc do not work within our own views (E4 views). Is it necessary to implement the shortcuts for ourselves or should the work in E4 parts automatically? Thanks for any help!
We discovered that this bug is already fixed (with Luna M4.4). For the issue concerning the "view shortcuts" we created the bug 426345.
