| RE: [corona-dev] Question on osgi bundle start level |
|
One more information: Such osgi bundle start sequence (inside
config.ini) is required: org.eclipse.osgi.services@2:start,
org.eclipse.equinox.log@3:start,
org.eclipse.corona.logger.log4j@4:start Starting osgi
services before equinox log is needed. From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kalka, Edyta Update: after running new eclipse instance
with options –clean –console
the bundle exception did not happen and org.eclipse.equinox.log is started. From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kalka, Edyta Question concerns implementation of osgi
log service and log reader service: org.eclipse.equinox.log. If I create run/debug configuration for
equinox osgi framework and set for instance the following: -
for
org.eclipse.equinox.log: start level = 2, start = true -
for
org.eclipse.corona.logger.log4j: start level = 3, start = true Log services are available during calling
start on eclipse.corona.logger.log4j activator and org.eclipse.equinox.log
state is ACTIVE (int value: 32). If I don’t set start level, and
start for equinox log bundle – services are not registered and bundle
state is RESOLVED. I tried to set this inside config.ini but
I have received org.osgi.framework.BundleException
(presented bellow). I have added equinox log bundle to dependencies of eclipse.corona.logger.log4j bundle. Having it working with specific run/debug
configuration is enough for development but not enough as general solution. Edyta From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On
Behalf Of O'Flynn, Dennis 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 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 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. 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. |