Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365289 - The handler service cannot be null
Summary: The handler service cannot be null
Status: RESOLVED DUPLICATE of bug 362147
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows Server 2003
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-01 05:01 EST by Raj CLA
Modified: 2011-12-01 09:03 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raj CLA 2011-12-01 05:01:30 EST
Build Identifier: M20110912-1510

Hi,

We have a eclipse plugin project build on eclipse 3.2 Now we are migrating on eclipse 4.1 release build M20110912-1510
I had build the project using all new plugins and resolved all the dependencies. Now when I am trying to launch the project ide it thowing following exception.

!ENTRY org.eclipse.ui 4 0 2011-12-01 01:44:11.640
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException: The handler service cannot be null
        at org.eclipse.ui.internal.commands.WorkbenchCommandSupport.<init>(WorkbenchCommandSupport.java:75)
        at org.eclipse.ui.internal.Workbench.initializeDefaultServices(Workbench.java:1893)
        at org.eclipse.ui.internal.Workbench.init(Workbench.java:1526)
        at org.eclipse.ui.internal.Workbench.access$36(Workbench.java:1481)
        at org.eclipse.ui.internal.Workbench$66.run(Workbench.java:2592)
java.lang.NullPointerException: The handler service cannot be null
        at org.eclipse.ui.internal.commands.WorkbenchCommandSupport.<init>(WorkbenchCommandSupport.java:75)
        at org.eclipse.ui.internal.Workbench.initializeDefaultServices(Workbench.java:1893)
        at org.eclipse.ui.internal.Workbench.init(Workbench.java:1526)
        at org.eclipse.ui.internal.Workbench.access$36(Workbench.java:1481)
        at org.eclipse.ui.internal.Workbench$66.run(Workbench.java:2592)

I had resolved all my plugins dependencies. All plugins are in Active or resolved state and few are in Lazy.

I am working on Window Server 2003 32 bit machine.

Can you please let me know what is the root cause of this exception. I had changed the IPlateformRunnable to IApplication and code is building successfully. This problem occur every time whenever I will try to launch the rcp.

Thanks
Rajesh

Reproducible: Always

Steps to Reproduce:
1. Build a plugin project in eclipse 3.2 with defined product and application
2. upgrade plugins with eclipse 4.1
3. Try to run product from osgi.
Comment 1 Paul Webster CLA 2011-12-01 06:08:40 EST
Did you add extra bundles to your RCP app?  You will need equinox.event and equinox.ds.

PW
Comment 2 Raj CLA 2011-12-01 06:32:04 EST
Hi Paul,

I had test this exception is occurs every time I have used following bundles with different combination to fix it.

osgi.bundles=reference\:file\:org.eclipse.equinox.util_1.0.300.v20110502.jar@4,reference\:file\:org.eclipse.equinox.event_1.2.100.v20110502.jar@4,reference\:file\:org.eclipse.e4.ui.workbench.addons.swt_0.10.0.v20110705-1300.jar@4,reference\:file\:org.eclipse.equinox.ds_1.3.1.R37x_v20110701.jar@2\:start,reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110502-1955.jar@1\:start,org.eclipse.equinox.common@2:start, org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start
org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.eclipse.equinox.simpleconfigurator/bundles.info

Also to have all dependencies resolved I am generating bundles.info file. And after checking the ss there is no unresolved dependency.

Only one issue I am getting while the launching eclipse is its not able to find my product in custom plugins. But this plugins is now in Active state.

Thanks
Rajesh
Comment 3 Paul Webster CLA 2011-12-01 07:30:08 EST
That's not the full set of bundles, and that's also probably not where they should be added.

See bug 362147 for a list of bundles that you will need to add to your product.

PW

*** This bug has been marked as a duplicate of bug 362147 ***
Comment 4 Raj CLA 2011-12-01 08:10:20 EST
(In reply to comment #3)
> That's not the full set of bundles, and that's also probably not where they
> should be added.
> 
> See bug 362147 for a list of bundles that you will need to add to your product.
> 
> PW
> 
> *** This bug has been marked as a duplicate of bug 362147 ***

This is the lists of required plugins in my product plugin

      <import plugin="org.eclipse.ui"/>
      <import plugin="org.eclipse.core.runtime"/>
      <import plugin="org.eclipse.ui.ide"/>
      <import plugin="com.alterpoint.ine.rcp.core"/>
      <import plugin="com.alterpoint.ine"/>
      <import plugin="org.eclipse.equinox.util" />
      <import plugin="org.eclipse.equinox.event" />
      <import plugin="org.eclipse.e4.ui.workbench.addons.swt" />
      <import plugin="org.eclipse.equinox.ds" />
      <import plugin="javax.annotation"/>
      <import plugin="org.apache.commons.logging"/>
      <import plugin="org.eclipse.core.filesystem"/>
      <import plugin="org.eclipse.equinox.app"/>

I am also checking your suggested link. Thanks for prompt response, I am stuck here.
Thanks
Rajesh
Comment 5 Paul Webster CLA 2011-12-01 08:20:30 EST
As I mentioned, your list of plugins is not complete.  You need all of the plugins listed in the e4 feature + the ones mentioned in that bug.

Do not re-open this until you've collected all of the plugins from that bug.

PW

*** This bug has been marked as a duplicate of bug 362147 ***