[jbosstools-issues] [JBoss JIRA] (JBIDE-17021) No editor descriptor for id org.eclipse.ui.internal.emptyEditorTab

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999651#comment-12999651 ] 

Fred Bricon edited comment on JBIDE-17021 at 9/5/14 9:01 PM:
-------------------------------------------------------------

I applied the PR yesterday but forgot to resolve the issue.

Went fine yesterday, but today I managed to see the empty editor for a few seconds, before it was replaced by Central, following an ungraceful stop. Still better than before. I suspect this is caused by the Central plugin being started after the blank editor is displayed and the perspectivelistener is late to the party, but I could be wrong.


was (Author: fbricon):
I applied the PR yesterday but forgot to resolve the issue.

Went fine yesterday, but today I manage to see the empty editor for a few seconds, before it's replaced by Central, following an ungraceful stop. Still better than before. I suspect this is caused by the Central plugin being started after the blank editor is displayed and the perspectivelistener is late to the party, but I could be wrong.

> No editor descriptor for id org.eclipse.ui.internal.emptyEditorTab
> ------------------------------------------------------------------
>
>                 Key: JBIDE-17021
>                 URL: https://issues.jboss.org/browse/JBIDE-17021
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central, upstream
>            Reporter: Max Rydahl Andersen
>            Assignee: Fred Bricon
>             Fix For: 4.2.0.CR1
>
>
> I keep from time to time to get two central editors to open up.
> 1) with "No editor descriptor for id org.eclipse.ui.internal.emptyEditorTab"
> 2) a few seconds later the real Central.
> My guess is that the editorinput for central is not behaving properly so it does not know how to restore itself causing it to be empty on start and then we force opening a new one even though already one there.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)