Hello Guys,
I have an Equinox OSGi application using Declarative Services with 3
plugins:
-a service interface plugin
-a service provider component
-a service consumer component (cardinality: 0..n, policy: dynamic)
Framework is launched.
id State Bundle
0 ACTIVE
Do you have an optional import for the package name?
If you do, and that bundle starts first, then it won't be wired to the package.
If you start up the bundle containing the package first, then start up the
provider, it will resolve the list of optional imports. Once started, even if
an
Hello,
No, I do not, but I also tried it with that without any success. Nor do I
with the 'refresh' Equinox console command. I always get the same exception
stack...
Actually what I try to do is to provide a proof-of-concept Equinox
application that is dynamically/at-runtime extendable (through
I would open a bug against Equinox-Compendium (at
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Equinox). This sounds
like a bug and it would be helpful if you could provide your testcase
attached to the bug.
Thanks.
Tom
|
| From: |
|
