--|
|>
| Subject: |
|>
>------------------------------------
Hello Paul,
Thanks a lot for the useful info! Now installing & starting my workspace
bundles also works.
Unfortunately I don't have too much experiences with OSGi and Equinox yet...
Btw: isn't there a common method that works for both cases (both with
deployed JAR bundles and workspace/exploded b
On Thu, Feb 9, 2012 at 4:27 AM, Csaba Szucs wrote:
>
> So it does not work like this:
> osgi>install
> file:/home/csaba/eclipse_distros/Indigo/workspace/osgi.example.service.implementation
>
> But it does work like this
> osgi>install
> file:/home/csaba/tmp/plugins/osgi.example.service.implementa
-|
|>
| Subject: |
|>
>------------------|
|Re: [equinox-dev] Service component depl
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 s
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 optio
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 org.eclipse.osgi_3.8.0.v20110908-1
