Community
Participate
Working Groups
Using WTP I20080329055928 I got following in my log ... not sure what I was doing, just seemed to appear when I was doing nothing ... but, I had been switching between Java and JEE perspective, and opening HTML files. !ENTRY org.eclipse.ui.workbench 2 0 2008-03-29 15:27:29.830 !MESSAGE A handler conflict occurred. This may disable some commands. !SUBENTRY 1 org.eclipse.ui.workbench 2 0 2008-03-29 15:27:30.268 !MESSAGE Conflict for 'org.eclipse.wst.jsdt.ui.edit.text.java.open.editor': HandlerActivation(commandId=org.eclipse.wst.jsdt.ui.edit.text.java.open.editor, handler=ActionHandler(org.eclipse.wst.jsdt.ui.actions.OpenAction@5c185c18), expression=AndExpression(org.eclipse.ui.SubActionBars$1@63986398,ActivePartExpression(org.eclipse.ui.navigator.CommonNavigator@bc00bc),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@60626062)),sourcePriority=1064961) HandlerActivation(commandId=org.eclipse.wst.jsdt.ui.edit.text.java.open.editor, handler=ActionHandler(org.eclipse.wst.jsdt.ui.actions.OpenAction@5c185c18), expression=AndExpression(org.eclipse.ui.SubActionBars$1@63986398,ActivePartExpression(org.eclipse.ui.navigator.CommonNavigator@bc00bc),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@60626062)),sourcePriority=1064961)
I'd like to mention that this warning quite common. It appears during the J2EE Tools smoke testing. I cannot give exact steps to reproduce. I have notice that it appears while I am working with the Project Explorer view.
Do you plan looking into this soon? I still see this in the error log with the M-3.0.1-20080717094056 build.
I too have seen this in the log (long after the problem occured), but I have had no success in finding the steps to recreate the problem. There is nothing obviously wrong with the plugin.xml so I need to be able to recreate the problem in order to fix.
*** Bug 218330 has been marked as a duplicate of this bug. ***
*** Bug 247954 has been marked as a duplicate of this bug. ***
Steps to reproduce: 1. Create a Dynamic Web Project. 2. In Project Explorer expand the WebContent folder. 3. Right-click on the WebContent folder and create a new JSP. 4. After the JSP is created and opened right-click on the page in Project Explorer, but don't click on anything in the menu. Close the menu. 5. Right-click on the WebContent folder again. Hover over the New sub-menu. 9 out of 10 times the conflict message appears in the log after the final step.
JSDT and JDT are adding handlers for action "org.eclipse.ui.navigator.Open". There seems to be some conflict in the SubActionBars.setGlobalActionHandler(String actionID, IAction handler) method. It looks like it is supposed to remove the existing JSDT action before it adds a new one, but that is not happening. I think it tries to remove the JDT action instead. This needs some more investigation. I'm not really sure how these handlers are supposed to work. Revised steps: 1. Have a dynamic web project with a JSP in its WebContent folder. The JSP does not need to be open. 2. Expland the WebContent folder and right-click on the JSP. Close the menu without selecting anything. 3. Right-click on the WebContent folder. The error is logged at this time. It only happens the first time you click on the folder after launching the workbench.
*** Bug 250464 has been marked as a duplicate of this bug. ***
*** Bug 282473 has been marked as a duplicate of this bug. ***
One year and no work on this? :) As I mentioned in bug 282473, I suspect this is affecting Bazaar plugin, as this error does not raise when I'm using ascii-only paths. When I change the project to a non-ascii path, this error shows up in log view, and I can't use the 'compare to > latest from branch' Bazaar option. This bug is being watched by Launchpad at https://bugs.launchpad.net/bzr-xmloutput/+bug/388300.
The handler exception that you identified is a known problem. We would certainly appreciate any contributions from you if you'd like to see defects such as this one be fixed at a faster rate. I'd be happy to point you to the relevant plugins. Thanks, Chris
Ok, I appreciate any help you can give me to find a solution, specially because I'm not very familiar with plugin development.
That's weird, I couldn't reproduce the bug in Ganymede with the provided steps in comment 7, and in Galileo the error raises when I'm using a non-ascii path for the project.
Any idea on which CVS modules to checkout and where to put breakpoints?
Hi Renato, In response to comment #13: I'm able to reproduce this problem pretty regularly in both versions. I know it only happens the first time I open a new workspace. I haven't had a chance to try with the non-ascii paths yet. Thanks for offering to help. We fixed a similar bug a little while back. Let me look that one up and see how that was fixed. It could be something similar. Thanks, Chris
It looks like the root of the problem is that JDT and JSDT both add open editor actions with the same activation parameters. This leads to the conflict. I think I need to update the enablement statement for the JSDT command. Perhaps it should be limited to use in the Script Explorer.
I solved my issue with Bazaar plugin. The problem was not related to JSDT at all, I'm sorry.
Created attachment 141429 [details] I added some additional enablement statements to help differentiate this from the jdt action.
Code checked into 3.2 stream.
1. Create a Dynamic Web Project. 2. Create a html page. 3. Click the collapse all button in Project Explorer. The handler conflict shows up.
More edits to the enablement statement.
This warning log still shows up in WTP 3.2.2 builds.
*** This bug has been marked as a duplicate of bug 310165 ***
