Eclipse Community Forums: Rich Client Platform (RCP)

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » Problems updating features

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

Problems updating features [message #437327]

Tue, 27 September 2005 13:44

Andreas Pakulat

Messages: 127
Registered: July 2009

Senior Member

Hi,

after I have my update-functionality in my self-written UpdateManager
working (at least the Features are "updated successfully") - using the
commands in org.eclipse.update.standalone - I have a problem starting my
RCP-app.

The update is done in the run-function but before the WorkbenchAdvisor
is instantiated. I thought that would be enough to do updates/installs
on startup without having to do a restart of the application. Installs
work, but updates don't. When the Display is created via
PlatformUI.createDisplay I get an exception:

java.lang.ExceptionInInitializerError
at org.eclipse.ui.internal.ProductInfo.getAppName(ProductInfo.j ava:65)
at
org.eclipse.ui.internal.WorkbenchPlugin.getAppName(Workbench Plugin.java:855)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:379)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:155)
at
de.zgdv.vesuv.behoerdenclient.BehoerdenclientApplication.run (BehoerdenclientApplication.java:90)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:226)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
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:334 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
Caused by: java.lang.IllegalStateException: Bundle
"update@D:/pakulat/eclipse_ws/Behoerdenclient/" has been uninstalled
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.chec kValid(AbstractBundle.java:1200)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.getE ntry(AbstractBundle.java:1293)
at
org.eclipse.core.internal.runtime.FindSupport.findInPlugin(F indSupport.java:206)
at
org.eclipse.core.internal.runtime.FindSupport.findNL(FindSup port.java:190)
at org.eclipse.core.internal.runtime.FindSupport.find(FindSuppo rt.java:82)
at org.eclipse.core.runtime.Platform.find(Platform.java:821)
at
org.eclipse.ui.internal.ProductProperties.loadMappings(Produ ctProperties.java:64)
at
org.eclipse.ui.internal.ProductProperties.<clinit>(ProductProperties.java:58)
... 16 more

I guess this is due to the update, so the question is: What am I doing
wrong (I only call UpdateCommand for every feature that I encounter on
my update-site and where a newer version than the installed feature is
available).

Andreas

Report message to a moderator

Re: Problems updating features [message #437469 is a reply to message #437327]

Thu, 29 September 2005 08:42

Andreas Pakulat

Messages: 127
Registered: July 2009

Senior Member

Andreas Pakulat schrieb:
> Hi,
>
> after I have my update-functionality in my self-written UpdateManager
> working (at least the Features are "updated successfully") - using the
> commands in org.eclipse.update.standalone - I have a problem starting my
> RCP-app.
>
> The update is done in the run-function but before the WorkbenchAdvisor
> is instantiated. I thought that would be enough to do updates/installs
> on startup without having to do a restart of the application. Installs
> work, but updates don't. When the Display is created via
> PlatformUI.createDisplay I get an exception:
>
> java.lang.ExceptionInInitializerError
> at org.eclipse.ui.internal.ProductInfo.getAppName(ProductInfo.j ava:65)
> at
> org.eclipse.ui.internal.WorkbenchPlugin.getAppName(Workbench Plugin.java:855)
>
> at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.ja va:379)
> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:155)
> at
> de.zgdv.vesuv.behoerdenclient.BehoerdenclientApplication.run (BehoerdenclientApplication.java:90)
>
> at
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:226)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
>
> 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:334 )
> at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
> at org.eclipse.core.launcher.Main.run(Main.java:973)
> at org.eclipse.core.launcher.Main.main(Main.java:948)
> Caused by: java.lang.IllegalStateException: Bundle
> "update@D:/pakulat/eclipse_ws/Behoerdenclient/" has been uninstalled
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.chec kValid(AbstractBundle.java:1200)
>
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getE ntry(AbstractBundle.java:1293)
>
> at
> org.eclipse.core.internal.runtime.FindSupport.findInPlugin(F indSupport.java:206)
>
> at
> org.eclipse.core.internal.runtime.FindSupport.findNL(FindSup port.java:190)
> at
> org.eclipse.core.internal.runtime.FindSupport.find(FindSuppo rt.java:82)
> at org.eclipse.core.runtime.Platform.find(Platform.java:821)
> at
> org.eclipse.ui.internal.ProductProperties.loadMappings(Produ ctProperties.java:64)
>
> at
> org.eclipse.ui.internal.ProductProperties.<clinit>(ProductProperties.java:58)
>
> ... 16 more
>
> I guess this is due to the update, so the question is: What am I doing
> wrong (I only call UpdateCommand for every feature that I encounter on
> my update-site and where a newer version than the installed feature is
> available).

Answering myself once again...

The solution I took was to check wether update or installation actually
did something and if so, return IPlatformRunnable.EXIT_RESTART, which
restarts the application and then no update/install is done anymore and
everything works just fine...

Andreas

Report message to a moderator

Previous Topic:	Login Dialog and splash screen
Next Topic:	documentation on update manager

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Dec 02 23:33:43 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter