Eclipse Community Forums: Rich Client Platform (RCP)

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » RCP Product Export Problems

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

RCP Product Export Problems [message #461652]

Mon, 15 January 2007 20:21

Troy Bourdon

Messages: 12
Registered: July 2009

Junior Member

I've been having a problem trying to export a my project. It looks as
though all the necessary files and jars are getting exported but I
continue to get the following message when I run the generated executable.

eclipse.buildId=unknown
java.version=1.5.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.core.runtime 2007-01-15 15:15:37.547
!MESSAGE Product com.companyname.product could not be found.

!ENTRY org.eclipse.osgi 4 0 2007-01-15 15:15:37.547
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: No application id has been found.
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:56)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
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.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)

Everything was done through the .product editor. In the Configuration tab
I added my plugin and then added the required plugins but I still get the
errors above.

- Troy

Report message to a moderator

Re: RCP Product Export Problems [message #461671 is a reply to message #461652]

Tue, 16 January 2007 06:15

Alex Blewitt

Messages: 946
Registered: July 2009

Senior Member

Try starting it manually with

eclipse -consoleLog -noExit -console

You should see the log messages being dumped out. Chances are, it's not starting your plugin and thus the applciation ID isn't found.

Use 'ss' to show the status of individual plugins -- each are identified by integer. You can try 'start 123' to start bundle 123, or use (IIRC) diag to print diagnostics of which bundles can't be started. ? will give a list of all commands on the console; you should finish it with 'shutdown'.

The most likely explaination is that the plugin is missing a dependent bundle, or that your bundle isn't being started.

Have you changed the osgi.bundles in the config.ini? It should contain at least the core runtime and update.configurator -- the latter scans through (and installs) all bundles in the plugins/ directory. If you've removed either of those, it's quite likely that it can't be found.

Alex.

Report message to a moderator

Re: RCP Product Export Problems [message #461766 is a reply to message #461671]

Tue, 16 January 2007 14:44

Troy Bourdon

Messages: 12
Registered: July 2009

Junior Member

Alex -

Thank you for the input but I'm afraid the problem is more nefarious than
an excluded bundle. All bundles are present and accounted for in the
config.ini file, this file was not edited by me but was generated by the
"Eclipse Product Export Wizard". Upon running the ss command at the osgi
prompt I find that all bundles have a state of "ACTIVE" or "RESOLVED".

From the output log it seems the application is having problems resolving
the product ID. This is pure conjecture on my part as I'm new to Eclipse
RCP, but the output log seems to point in that direction.

This is very frustrating as everything has been generated "automagically"
via the PDE and its all very "Black Box" at this point.

- Troy

Report message to a moderator

Re: RCP Product Export Problems [message #461781 is a reply to message #461652]

Wed, 17 January 2007 05:02

Jeff Higgins

Messages: 51
Registered: July 2009

Member

Troy Bourdon wrote:
> I've been having a problem trying to export a my project.

> java.lang.RuntimeException: No application id has been found.
> at

Look in your build.properties file and
see if the bin.includes entry contains the root
directory. This missing full stop brought my
export to a full stop just yesterday..
JH

output.. = bin/
source.. = src/
bin.includes = .,\ <-------------This
META-INF/,\
about.html,\
about.mappings,\

Report message to a moderator

Re: RCP Product Export Problems [message #461794 is a reply to message #461766]

Wed, 17 January 2007 10:40

Alex Blewitt

Messages: 946
Registered: July 2009

Senior Member

If your bundle is RESOLVED but not ACTIVE, check also that your Manifest.MF has one of these entries (or heck, all of them):

Eclipse-AutoStart: true
Eclipse-LazyStart: true
Bundle-ActivationPolicy: lazy

Also, check that the plugin.xml is present in your bundle in the Jar. If it's not there, you'd see that message. (And if it's not there, adding 'plugin.xml' to the list of the 'bin.includes' is possible. NB you shouldn't have '.' in the includes list for bin.includes, unlike another poster suggested, because then you'll also export all your source and the binary classes a second time.

Alex.

Report message to a moderator

Re: RCP Product Export Problems [message #461805 is a reply to message #461794]

Wed, 17 January 2007 14:44

Troy Bourdon

Messages: 12
Registered: July 2009

Junior Member

Alex -

Thanks for your help and insight. It got me on the right track to solve
the problem. I took more time to explore the runtime and specifically what
could be accomplished by running app.exe -console -noExit to get the osgi
prompt. I still don't fully understand all the options provided but
issuing the ss command did in fact show that one of the bundles had a
state of "INSTALLED" vice "ACTIVE" or "RESOLVED". By running start with
the id of that bundle I was able to see it could not be resolved because
it depended on a bundle which was not part of the product configuration.
After adding the required bundle I was able to repeat the iteration until
all bundles were either "INSTALLED" or "ACTIVE".

The disappointing part of this was that the original list of bundles was
generated by the "Product Export Wizard" by selecting my application's
bundle in the Configuration tab and clicking the "Add Required Plug-ins"
button. It appears that not ALL the required plug-ins were added.

I suspect that most references to this problem that I've seen on the net
can be traced back to simply not having all the bundle dependencies
resolved. The problem is, there is no EASY way to determine these
dependency deficiencies BEFORE runtime.

At least its nice to know that these dependencies can be fleshed out at
the osgi prompt.

Thanks;

- Troy

Report message to a moderator

Re: RCP Product Export Problems [message #461885 is a reply to message #461805]

Wed, 17 January 2007 18:20

Alex Blewitt

Messages: 946
Registered: July 2009

Senior Member

Normally if that happens, the log will show a message like 'The following bundle could not be started because one of its dependencies could not be met'. It would be a weird scenario for this to occur just for a product bundle not finding the app.

If you click on 'add required bundles' again, does it add it or remove the one you've just added? Also, it would be interesting if you were to deselect all of them, and then did the 'add required' to find out which one(s) weren't added.

I can imagine that it might include some fragments. There's also the possibility of some other bundles that have ;optional at the end, but if that's the case, I'd expect it still to start OK, just perhaps not run as expected :-)

Given the amount of time you've spent tracking this down, it would be good at least to know which bundle was missing (if it wasn't one of your internal ones) and/or raise a bug at https://bugs.eclipse.org to record it for others.

Alex.

Report message to a moderator