Eclipse Community Forums: Eclipse 4 » Problems between 4.0 based target platform and 4.1 based target platform.

Help

Home

Home » Eclipse Projects » Eclipse 4 » Problems between 4.0 based target platform and 4.1 based target platform.

Show: Today's Messages :: Show Polls :: Message Navigator

Problems between 4.0 based target platform and 4.1 based target platform. [message #643031]

Fri, 03 December 2010 17:17

Daniel Ford

Messages: 148
Registered: July 2009
Location: New York

Senior Member

I'm trying to migrate a minimal e4 based RCP from a 4.0 target platform
to a 4.1 based target platform. I've resolved most of my issues and now
have a "good" target for 4.1.

Now, I have an interesting problem. My RCP runs with no problems on the
4.0 based target, but when I switch to the 4.1 target, and use the same
launch configuration, I get an NPE at start-up in
E4Workbench.processHierarchy() when it fails to obtain an instance of
the EHandlerService and then tries to de-reference null. I've checked
out the code and stepped through it in the debugger to verify what was
happening, but I got out of my zone when it came to resolving the
instance other than to determine that it wasn't finding it.

I'm still an e4 newbie, so I'm wary to claim I've found a bug, and
expect I've missed something, especially since this seems pretty
fundamental. It's gotta be me, but, what?!

Dan

!ENTRY org.eclipse.osgi 4 0 2010-12-03 12:05:16.340
!MESSAGE Application error
!STACK 1
java.lang.NullPointerException
at
org.eclipse.e4.ui.internal.workbench.E4Workbench.processHier archy(E4Workbench.java:193)
at
org.eclipse.e4.ui.internal.workbench.E4Workbench.init(E4Work bench.java:117)
at
org.eclipse.e4.ui.internal.workbench.E4Workbench.<init>(E4Workbench.java:72)
at
org.eclipse.e4.ui.internal.workbench.swt.E4Application.creat eE4Workbench(E4Application.java:264)
at
org.eclipse.e4.ui.internal.workbench.swt.E4Application.start (E4Application.java:116)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.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(EclipseS tarter.java:369)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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)

Report message to a moderator

Re: Problems between 4.0 based target platform and 4.1 based target platform. [message #643168 is a reply to message #643031]

Sun, 05 December 2010 15:37

Thomas Schindl

Messages: 6651
Registered: July 2009

Senior Member

Do you have the 2 addons needed since some weeks in your .e4xmi. I'd
advise all early adopters to follow e4-dev closely.

I can't really tell if this is cause but here's Pauls mail and the
follow up discussion [1].

Tom

[1] http://www.mail-archive.com/e4-dev@eclipse.org/msg04085.html

Am 03.12.10 18:17, schrieb Daniel Ford:
> I'm trying to migrate a minimal e4 based RCP from a 4.0 target platform
> to a 4.1 based target platform. I've resolved most of my issues and now
> have a "good" target for 4.1.
>
> Now, I have an interesting problem. My RCP runs with no problems on the
> 4.0 based target, but when I switch to the 4.1 target, and use the same
> launch configuration, I get an NPE at start-up in
> E4Workbench.processHierarchy() when it fails to obtain an instance of
> the EHandlerService and then tries to de-reference null. I've checked
> out the code and stepped through it in the debugger to verify what was
> happening, but I got out of my zone when it came to resolving the
> instance other than to determine that it wasn't finding it.
>
> I'm still an e4 newbie, so I'm wary to claim I've found a bug, and
> expect I've missed something, especially since this seems pretty
> fundamental. It's gotta be me, but, what?!
>
> Dan
>
>
> !ENTRY org.eclipse.osgi 4 0 2010-12-03 12:05:16.340
> !MESSAGE Application error
> !STACK 1
> java.lang.NullPointerException
> at
> org.eclipse.e4.ui.internal.workbench.E4Workbench.processHier archy(E4Workbench.java:193)
>
> at
> org.eclipse.e4.ui.internal.workbench.E4Workbench.init(E4Work bench.java:117)
> at
> org.eclipse.e4.ui.internal.workbench.E4Workbench.<init>(E4Workbench.java:72)
>
> at
> org.eclipse.e4.ui.internal.workbench.swt.E4Application.creat eE4Workbench(E4Application.java:264)
>
> at
> org.eclipse.e4.ui.internal.workbench.swt.E4Application.start (E4Application.java:116)
>
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.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(EclipseS tarter.java:369)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> 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)

Report message to a moderator