Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [corona-dev] Question on osgi bundle start level

I assume the following should work to ensure deployment / startup order:

 

1)     Creating a dependency between plug-ins

2)     Declarative services

3)     Startup order within config.ini

 

Any incomplete deployment of dependent bundles will cause a bundle to be “installed”, but not “resolved”.  Thus it cannot be “started”.

 

From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kalka, Edyta
Sent: Tuesday, August 08, 2006 4:45 AM
To: Corona development
Subject: RE: [corona-dev] Question on osgi bundle start level

 

Is there any other way of assuring or causing any osgi service to be started before using it?

 

Edyta

 

From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kalka, Edyta
Sent: 7 sierpnia 2006 17:10
To: Corona development
Subject: [corona-dev] Question on osgi bundle start level

 

After adding to config.ini this:

org.eclipse.equinox.log@3:start

 

I receive after opening workspace such exception:

org.osgi.framework.BundleException: Bundle "org.eclipse.equinox.log" version "1.0.0.v20060601a" has already been installed from: update@plugins/org.eclipse.equinox.log_1.0.0.v20060601a.jar

at org.eclipse.osgi.framework.internal.core.Framework.createAndVerifyBundle(Framework.java:557)

at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:824)

at org.eclipse.osgi.framework.internal.core.Framework$2.run(Framework.java:739)

at java.security.AccessController.doPrivileged(Native Method)

at org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:790)

at org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:734)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:221)

at org.eclipse.core.runtime.adaptor.EclipseStarter.installBundles(EclipseStarter.java:1067)

at org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBundles(EclipseStarter.java:649)

at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:305)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:173)

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)

 

Why in case of org.eclipse.equinox.common such setting of start level can be done and in case of org.eclipse.equinox.log not?

 

Edyta

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

Back to the top