| Conflicting Handlers on Migration [message #1697202] |
Tue, 02 June 2015 08:13  |
Eclipse User |
|
|
|
Hi!
We decided that it is about time to change the current targetplatform (3.6) of our rcp product to the newest targetplatform (4.4.2). We want to run the rcp with the compatibility layer and as soon as we do we get a lot of "Conflicting Handlers". It also seems that every command/action/handler is loaded twice, because also almost every error-message exists twice? With 3.6 we didn't get these messages and the handlers also seem to work, but the messages are annoying.
I shortened the log a little because there are realy a lot of conflicts:
!SESSION 2015-06-02 13:38:05.003 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_40
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_AT
Framework arguments: -product appl.ui.product
Command-line arguments: -product appl.ui.product -data D:\workspace\xx/../runtime-xx -dev file:D:/workspace/c2is/.metadata/.plugins/org.eclipse.pde.core/xx/dev.properties -os win32 -ws win32 -arch x86 -consoleLog
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.215
!MESSAGE Conflicting handlers for org.eclipse.ui.views.properties.NewPropertySheetCommand: {org.eclipse.ui.views.properties.NewPropertySheetHandler} vs {org.eclipse.ui.views.properties.NewPropertySheetHandler}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.help.helpSearch: {org.eclipse.ui.internal.handlers.HelpSearchHandler@1eb5790} vs {org.eclipse.ui.internal.handlers.HelpSearchHandler}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.help.aboutAction: {org.eclipse.ui.internal.about.AboutHandler} vs {org.eclipse.ui.internal.about.AboutHandler@1b5db0}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.newWizard: {org.eclipse.ui.internal.handlers.WizardHandler$New} vs {org.eclipse.ui.internal.handlers.WizardHandler$New@18286c4}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.file.import: {org.eclipse.ui.internal.handlers.WizardHandler$Import} vs {org.eclipse.ui.internal.handlers.WizardHandler$Import@178aea6}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.file.export: {org.eclipse.ui.internal.handlers.WizardHandler$Export} vs {org.eclipse.ui.internal.handlers.WizardHandler$Export@53495b}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.file.save: {org.eclipse.ui.internal.handlers.SaveHandler@173ae5b} vs {org.eclipse.ui.internal.handlers.SaveHandler}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.file.saveAs: {org.eclipse.ui.internal.handlers.SaveAsHandler@1f459fc} vs {org.eclipse.ui.internal.handlers.SaveAsHandler}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.file.saveAll: {org.eclipse.ui.internal.handlers.SaveAllHandler} vs {org.eclipse.ui.internal.handlers.SaveAllHandler@4487f4}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.file.restartWorkbench: {org.eclipse.ui.internal.handlers.RestartWorkbenchHandler} vs {org.eclipse.ui.internal.handlers.RestartWorkbenchHandler@9b9909}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.file.properties: {org.eclipse.ui.internal.handlers.PropertyDialogHandler} vs {org.eclipse.ui.internal.handlers.PropertyDialogHandler@1361cf6}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.216
!MESSAGE Conflicting handlers for org.eclipse.ui.file.exit: {org.eclipse.ui.internal.handlers.QuitHandler} vs {org.eclipse.ui.internal.handlers.QuitHandler@10d89e2}
...
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.file.closeOthers: {org.eclipse.ui.internal.CloseOthersHandler@1e47a03} vs {org.eclipse.ui.internal.CloseOthersHandler}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.ToggleCoolbarAction: {org.eclipse.ui.internal.handlers.ToggleCoolbarHandler@1425813} vs {org.eclipse.ui.internal.handlers.ToggleCoolbarHandler}
...
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.window.nextPerspective: {org.eclipse.ui.internal.CyclePerspectiveHandler@137203b} vs {org.eclipse.ui.internal.CyclePerspectiveHandler:true}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.window.previousPerspective: {org.eclipse.ui.internal.CyclePerspectiveHandler:false} vs {org.eclipse.ui.internal.CyclePerspectiveHandler@823d72}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.window.closeAllPerspectives: {org.eclipse.ui.internal.handlers.CloseAllPerspectivesHandler} vs {org.eclipse.ui.internal.handlers.CloseAllPerspectivesHandler@10562}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.window.customizePerspective: {org.eclipse.ui.internal.handlers.EditActionSetsHandler} vs {org.eclipse.ui.internal.handlers.EditActionSetsHandler@9e07c6}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.window.closePerspective: {org.eclipse.ui.internal.handlers.ClosePerspectiveHandler} vs {org.eclipse.ui.internal.handlers.ClosePerspectiveHandler@19b187a}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.window.openEditorDropDown: {org.eclipse.ui.internal.WorkbookEditorsHandler@10dc7d6} vs {org.eclipse.ui.internal.WorkbookEditorsHandler}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.window.newEditor: {org.eclipse.ui.internal.handlers.NewEditorHandler} vs {org.eclipse.ui.internal.handlers.NewEditorHandler@1a8042c}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.window.maximizePart: {org.eclipse.ui.internal.handlers.MaximizePartHandler@84f0d9} vs {org.eclipse.ui.internal.handlers.MaximizePartHandler}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.window.resetPerspective: {org.eclipse.ui.internal.handlers.ResetPerspectiveHandler} vs {org.eclipse.ui.internal.handlers.ResetPerspectiveHandler@afdf9a}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.window.savePerspective: {org.eclipse.ui.internal.handlers.SavePerspectiveHandler} vs {org.eclipse.ui.internal.handlers.SavePerspectiveHandler@1efd2c2}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.279
!MESSAGE Conflicting handlers for org.eclipse.ui.help.quickStartAction: {org.eclipse.ui.internal.handlers.IntroHandler@1b52284} vs {org.eclipse.ui.internal.handlers.IntroHandler}
...
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.294
!MESSAGE Conflicting handlers for org.eclipse.ui.edit.text.removeTrailingWhitespace: {org.eclipse.ui.internal.editors.text.RemoveTrailingWhitespaceHandler} vs {org.eclipse.ui.internal.editors.text.RemoveTrailingWhitespaceHandler}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.560
!MESSAGE Conflicting handlers for org.eclipse.ui.file.exit: {org.eclipse.ui.internal.handlers.QuitHandler@8f018e} vs {org.eclipse.ui.internal.handlers.QuitHandler@10d89e2}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.560
!MESSAGE Conflicting handlers for org.eclipse.ui.help.aboutAction: {org.eclipse.ui.internal.about.AboutHandler@1860823} vs {org.eclipse.ui.internal.about.AboutHandler@1b5db0}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.560
!MESSAGE Conflicting handlers for org.eclipse.ui.file.save: {org.eclipse.ui.internal.handlers.SaveHandler@173ae5b} vs {org.eclipse.ui.internal.handlers.SaveHandler}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.560
!MESSAGE Conflicting handlers for org.eclipse.ui.file.saveAll: {org.eclipse.ui.internal.handlers.SaveAllHandler@168b571} vs {org.eclipse.ui.internal.handlers.SaveAllHandler@4487f4}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.575
!MESSAGE Conflicting handlers for org.eclipse.ui.window.resetPerspective: {org.eclipse.ui.internal.handlers.ResetPerspectiveHandler@1ac686b} vs {org.eclipse.ui.internal.handlers.ResetPerspectiveHandler@afdf9a}
!ENTRY org.eclipse.ui 4 4 2015-06-02 13:38:19.575
!MESSAGE Conflicting handlers for org.eclipse.ui.window.closePerspective: {org.eclipse.ui.internal.handlers.ClosePerspectiveHandler@c75c01} vs {org.eclipse.ui.internal.handlers.ClosePerspectiveHandler@19b187a}
I hope somebody can give me a hint where to start looking for the problem? I have no idea because it subjects our custom handlers and the eclipse handlers.
Thanks and best regards
|
|
|
| Re: Conflicting Handlers on Migration [message #1697227 is a reply to message #1697202] |
Tue, 02 June 2015 10:50  |
| Eclipse User |
|
|
|
That warning indicates that the platform found at least two handler instances for the same command and was unable to definitively choose one as the winner based on the <activeWhen> expressions. Basically the platform scores each handler based on the complexity of the activeWhen expression. When deciding what should be the active handler, the platform sorts the applicable handlers based on this score and selects the smallest score. If you have a command with a default handler, you must ensure all other handlers specify an <activeWhen>:
Quote:A handler that specifies no conditions is a default handler. A default handler is only active if no other handler has all of its conditions satisfied. If two handlers still have conditions that are satisfied, then the conditions are compared. The idea is to select a handler whose condition is more specific or more local. To do this, the variables referred to by the condition are looked at. The condition that refers to the most specific variable "wins". The order of specificity (from least specific to most specific) is suggested in org.eclipse.ui.ISources.
If this still doesn't resolve the conflict, then no handler is active. If a particular tracing option is turned on, then this leads to a message in the log. A conflict can also occur if there are two default handlers. It is the responsibility of the plug-in developers and integration testers to ensure that this does not happen.
http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fextension-points%2Forg_eclipse_ui_handlers.html
I'm not sure why you're getting multiple instances of the same handler instance being registered.
Brian.
|
|
|
Powered by
FUDForum. Page generated in 1.02969 seconds
Home