Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Eclipse juno compatibility issue(migration from indigo to juno causing compatibility issues)
Eclipse juno compatibility issue [message #1069154] Mon, 15 July 2013 09:29 Go to next message
prabuddha singh is currently offline prabuddha singhFriend
Messages: 4
Registered: December 2012
Junior Member
Hi,
i was using some api's for splitting the editor area into two with eclipse indigo but now i have migrated to juno so i am facing compatibility issues.the jars required

org.eclipse.ui.internal.ilayoutcontainer,org.eclipse.ui.internal.editorsashcontainer org.eclipse.ui.internal.LayoutPart are not being resolved, maybe these plugins have been moved to some other jar in juno which i need to add.

all these plugins alongwith org.eclipse.ui.internal.PartPane,org.eclipse.ui.internal.PartSite,org.eclipse.ui.internal.WorkbenchPage;were being resolved in indigo from the bundle org.eclipse.ui but in juno these cant be resolved through org.eclipse.ui. so in juno is there a different bundle which i need to add?
please help.

here is the code.
the classes in bold cant be resolved
private void splitEditorArea() {
IWorkbenchPage workbenchPage = PlatformUI.getWorkbench().getActiveWorkbenchWindow().getActivePage();
IWorkbenchPart part = workbenchPage.getActivePart();
PartPane partPane = ((PartSite) part.getSite()).getPane();
LayoutPart layoutPart = partPane.getPart();
try {
IDE.openEditor(workbenchPage, wsdlFile);
} catch (PartInitException e1) {
e1.printStackTrace();
}
IEditorReference[] editorReferences = workbenchPage.getEditorReferences();

// Do it only if we have more that one editor
if (editorReferences.length > 1) {
// Get PartPane that correspond to the active editor
PartPane currentEditorPartPane = ((PartSite) workbenchPage.getActiveEditor().getSite()).getPane();
EditorSashContainer editorSashContainer = null;
ILayoutContainer rootLayoutContainer = layoutPart.getContainer();
if (rootLayoutContainer instanceof LayoutPart) {
ILayoutContainer editorSashLayoutContainer = ((LayoutPart) rootLayoutContainer).getContainer();
if (editorSashLayoutContainer instanceof EditorSashContainer) {
editorSashContainer = ((EditorSashContainer) editorSashLayoutContainer);
}
}
/*
* Create a new part stack (i.e. a workbook) to home the
* currentEditorPartPane which hold the active editor
*/
PartStack newPart = createStack(editorSashContainer);
editorSashContainer.stack(currentEditorPartPane, newPart);
if (rootLayoutContainer instanceof LayoutPart) {
ILayoutContainer cont = ((LayoutPart) rootLayoutContainer).getContainer();
if (cont instanceof PartSashContainer) {
// "Split" the editor area by adding the new part
((PartSashContainer) cont).add(newPart);
}
}
}
}

thanks and regards,

prabuddha

[Updated on: Mon, 15 July 2013 09:40]

Report message to a moderator

Re: Eclipse juno compatibility issue [message #1073221 is a reply to message #1069154] Wed, 24 July 2013 10:45 Go to previous messageGo to next message
Adrian JV is currently offline Adrian JVFriend
Messages: 1
Registered: July 2013
Junior Member
Hello,
I am facing the same problem. Did you solve it?

I am thinking whether they might have "moved" this functionality and we could use some other methods or they just "closed" it and I have to change the target platform of my app so that it uses a workbench that provides this capabilities.

I would appreciate your answer even to tell me whether you did solve it or not.

Regards,
Adrian
Re: Eclipse juno compatibility issue [message #1073386 is a reply to message #1073221] Wed, 24 July 2013 16:51 Go to previous messageGo to next message
David Wegener is currently offline David WegenerFriend
Messages: 1351
Registered: July 2009
Senior Member
You are referencing internal classes. Internal classes are not part of the API and can change/disappear at any time. There was a complete rewriting of the Eclipse programming model between Indigo and Juno. It is likely that these internal classes are no longer available.
Re: Eclipse juno compatibility issue [message #1074802 is a reply to message #1073221] Sat, 27 July 2013 20:26 Go to previous message
prabuddha singh is currently offline prabuddha singhFriend
Messages: 4
Registered: December 2012
Junior Member
Hi Adrian,
I have now removed the functionality from my code,as mentioned the internal APi's are not suitable to be used and i couldnt find any other classes for replacement.i am searching for other classes but not too confident on that.
regards,
prabuddha
Previous Topic:Change default 'Group By' in Problems View
Next Topic:Eclipse Kepler Dependency Injection in 3.x & Views
Goto Forum:
  


Current Time: Wed Dec 17 19:57:56 GMT 2014

Powered by FUDForum. Page generated in 0.03599 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software