| Undefined context exception when activating a plug-in [message #493216] |
Fri, 23 October 2009 16:04 |
 Michael Matzen
Messages: 13
Registered: July 2009 |
Junior Member |
|
|
Hi all,
when i am loading a generated plug-in (with the extensionRegistry) i am
receiving a lot of 'Undefined context while filtering dialg/window
contexts' exception.
Here's a part of the stack trace:
org.eclipse.core.commands.common.NotDefinedException: Cannot get the
parent identifier from an undefined context.
org.eclipse.mylyn.context.ui.actionSet
at org.eclipse.core.commands.contexts.Context.getParentId(Conte xt.java:201)
at
org.eclipse.jface.bindings.BindingManager.createFilteredCont extTreeFor(BindingManager.java:825)
at
org.eclipse.jface.bindings.BindingManager.recomputeBindings( BindingManager.java:1721)
There are a few bugzilla tickets about this topic and i think they are
thrown because i am loading the plug-in when eclipse is already running
so the bindings are active when the BindingManager calls 'undefine'
while recomputing the bindings.
Is there anything i can do about it ?
Regards,
Michael
|
|
|
Powered by
FUDForum. Page generated in 0.02951 seconds
] 
Search
Help
Register
Login
Home
