Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse 4 » Error on Startup - Could not run processor
Error on Startup - Could not run processor [message #762601] Thu, 08 December 2011 06:19 Go to next message
Christoph Keimel is currently offline Christoph Keimel
Messages: 277
Registered: December 2010
Location: Germany
Senior Member
Hi,

I recently updated from SDK 4.1 to 4.2. I have a pure e4 Application we are experimenting with. On startup I now get a "Could not run processor" warning (see below).

This does not seem to have any effects to the running application ... at least I haven't noticed them yet. I'd still like to get to the bottom of the warning. Could someone please point me in the right direction?

Thanks
Christoph

!ENTRY org.eclipse.e4.ui.workbench 2 0 2011-12-08 12:12:27.719
!MESSAGE Could not run processor
!STACK 0
org.eclipse.e4.core.di.InjectionException: org.eclipse.core.runtime.AssertionFailedException: null argument:
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:228)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:198)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:86)
	at org.eclipse.e4.ui.internal.workbench.ModelAssembler.runProcessor(ModelAssembler.java:222)
	at org.eclipse.e4.ui.internal.workbench.ModelAssembler.processModel(ModelAssembler.java:87)
	at org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadMostRecentModel(ResourceHandler.java:246)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadApplicationModel(E4Application.java:351)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:215)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.start(E4Application.java:130)
	at de.emsw.gosa.product.etisch.ETischApplication.startE4Application(ETischApplication.java:324)
	at de.emsw.gosa.product.etisch.ETischApplication.startApp(ETischApplication.java:309)
	at de.emsw.gosa.product.etisch.ETischApplication.start(ETischApplication.java:154)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Caused by: org.eclipse.core.runtime.AssertionFailedException: null argument:
	at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
	at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
	at org.eclipse.ui.internal.util.PrefUtil.getAPIPreferenceStore(PrefUtil.java:64)
	at org.eclipse.ui.PlatformUI.getPreferenceStore(PlatformUI.java:187)
	at org.eclipse.ui.internal.keys.BindingPersistence.readActiveScheme(BindingPersistence.java:378)
	at org.eclipse.ui.internal.keys.BindingPersistence.reRead(BindingPersistence.java:1380)
	at org.eclipse.ui.internal.keys.BindingPersistence.read(BindingPersistence.java:1284)
	at org.eclipse.ui.internal.BindingToModelProcessor.process(BindingToModelProcessor.java:61)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
	... 25 more
12:12:27.719 WARN  org.eclipse.equinox.logger - Could not run processor
org.eclipse.e4.core.di.InjectionException: org.eclipse.core.runtime.AssertionFailedException: null argument:
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) ~[na:na]
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:228) ~[na:na]
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:198) ~[na:na]
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:86) ~[na:na]
	at org.eclipse.e4.ui.internal.workbench.ModelAssembler.runProcessor(ModelAssembler.java:222) ~[na:na]
	at org.eclipse.e4.ui.internal.workbench.ModelAssembler.processModel(ModelAssembler.java:87) ~[na:na]
	at org.eclipse.e4.ui.internal.workbench.ResourceHandler.loadMostRecentModel(ResourceHandler.java:246) ~[na:na]
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.loadApplicationModel(E4Application.java:351) ~[na:na]
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:215) ~[na:na]
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application.start(E4Application.java:130) ~[na:na]
	at de.emsw.gosa.product.etisch.ETischApplication.startE4Application(ETischApplication.java:324) ~[na:na]
	at de.emsw.gosa.product.etisch.ETischApplication.startApp(ETischApplication.java:309) ~[na:na]
	at de.emsw.gosa.product.etisch.ETischApplication.start(ETischApplication.java:154) ~[na:na]
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) ~[na:na]
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) ~[na:na]
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) ~[na:na]
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) ~[na:na]
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) ~[na:na]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_29]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_29]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_29]
	at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_29]
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) ~[org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar:na]
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) ~[org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar:na]
	at org.eclipse.equinox.launcher.Main.run(Main.java:1410) ~[org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar:na]
	at org.eclipse.equinox.launcher.Main.main(Main.java:1386) ~[org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar:na]
Caused by: org.eclipse.core.runtime.AssertionFailedException: null argument:
	at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) ~[na:na]
	at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) ~[na:na]
	at org.eclipse.ui.internal.util.PrefUtil.getAPIPreferenceStore(PrefUtil.java:64) ~[na:na]
	at org.eclipse.ui.PlatformUI.getPreferenceStore(PlatformUI.java:187) ~[na:na]
	at org.eclipse.ui.internal.keys.BindingPersistence.readActiveScheme(BindingPersistence.java:378) ~[na:na]
	at org.eclipse.ui.internal.keys.BindingPersistence.reRead(BindingPersistence.java:1380) ~[na:na]
	at org.eclipse.ui.internal.keys.BindingPersistence.read(BindingPersistence.java:1284) ~[na:na]
	at org.eclipse.ui.internal.BindingToModelProcessor.process(BindingToModelProcessor.java:61) ~[na:na]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_29]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_29]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_29]
	at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_29]
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) ~[na:na]
	... 25 common frames omitted

Report message to a moderator

Re: Error on Startup - Could not run processor [message #762637 is a reply to message #762601] Thu, 08 December 2011 07:31 Go to previous messageGo to next message
Thomas Kölling is currently offline Thomas Kölling
Messages: 45
Registered: December 2011
Location: Munich
Member
Hi Christoph,

i got the same exception (and application runs too), but only if i add the workbench.swt.addons (for drag and dropping parts and stuff). would be great if someone can give workaround for this.

greetings,
Thomas

Report message to a moderator

Re: Error on Startup - Could not run processor [message #762705 is a reply to message #762601] Thu, 08 December 2011 09:28 Go to previous messageGo to next message
Paul Webster is currently offline Paul Webster
Messages: 6813
Registered: July 2009
Location: Ottawa
Senior Member
What set of bundles do you have in your Eclipse 4 RCP app that's different than the http://git.eclipse.org/c/platform/eclipse.platform.ui.git/tree/examples/org.eclipse.e4.demo.contacts/contacts.product file?

PW

Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions

Report message to a moderator

Re: Error on Startup - Could not run processor [message #762723 is a reply to message #762705] Thu, 08 December 2011 09:51 Go to previous messageGo to next message
Thomas Kölling is currently offline Thomas Kölling
Messages: 45
Registered: December 2011
Location: Munich
Member
Hi Paul,

i've checked out the contacts demo. the exception doesn't appear there. i've cross checked the product files. the only differences are

<plugin id="org.pushingpixels.trident"/>
<plugin id="org.eclipse.e4.xwt"/>
<plugin id="org.eclipse.e4.xwt.css"/>
<plugin id="org.eclipse.e4.xwt.ui.workbench"/>

makes sense, cause i'm working with xwt.

greetings,
Thomas

Report message to a moderator

Re: Error on Startup - Could not run processor [message #762734 is a reply to message #762723] Thu, 08 December 2011 10:03 Go to previous messageGo to next message
Paul Webster is currently offline Paul Webster
Messages: 6813
Registered: July 2009
Location: Ottawa
Senior Member
And you don't have the workbench.swt.addons ? As it turns out workbench.swt.addons turns it into a compat layer app at the moment, until we fix https://bugs.eclipse.org/bugs/show_bug.cgi?id=358739

PW

Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions

Report message to a moderator

Re: Error on Startup - Could not run processor [message #762735 is a reply to message #762723] Thu, 08 December 2011 10:03 Go to previous messageGo to next message
Thomas Kölling is currently offline Thomas Kölling
Messages: 45
Registered: December 2011
Location: Munich
Member
Okay,

i've created a new e4 project. added the workbench.addons.swt plugin from the run configuration plug-in tab. after that i've added some other plugins with the "add Required Plug-ins" Button. After running the Project as Eclipse Application. The Excecption above occours.

Greetings
Thomas

Report message to a moderator

Re: Error on Startup - Could not run processor [message #762737 is a reply to message #762734] Thu, 08 December 2011 10:05 Go to previous messageGo to next message
Thomas Kölling is currently offline Thomas Kölling
Messages: 45
Registered: December 2011
Location: Munich
Member
sure. the workbench addons are in my project. like i said in my first post.

Report message to a moderator

Re: Error on Startup - Could not run processor [message #762774 is a reply to message #762737] Thu, 08 December 2011 10:55 Go to previous message
Paul Webster is currently offline Paul Webster
Messages: 6813
Registered: July 2009
Location: Ottawa
Senior Member
That makes it not an e4 app, because it pulls in the compatibility layer. We'll hopefully get that fixed in M5 https://bugs.eclipse.org/bugs/show_bug.cgi?id=358739

PW

Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions

Report message to a moderator

Previous Topic:How to setup a pure e4 Target Definition
Next Topic:Create dropdown menu in toolbar
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Fri May 24 19:00:32 EDT 2013

Powered by FUDForum. Page generated in 0.01724 seconds