Thanks for the explanation of the uses:= clause. It still does not
work. I get the same errors as reported last week and I don't know
what I do wrong. I also tried to bundle each jar in the SDK
separately, but that didn't work either. I am open to all creative
solutions.
If used the follo
I have a very simple service provider that works outside of OSGi.
I tried using it in Felix but it fails with a ClassCastException.
Is this somehow related to the different class loaders in the different
bundles?
Any suggestions on how to get past this?
Thanks.
Tim Moloney The r
On 5/18/09 9:31 AM, Moloney, Tim M wrote:
I have a very simple service provider that works outside of OSGi.
I tried using it in Felix but it fails with a ClassCastException.
Is this somehow related to the different class loaders in the different
bundles?
Probably.
Any suggestions on how
Hi,
I'm runing the UPnP basedriver in an embedded device to detect UPnP services on
the network and as it is shown in the upnp.properties file the default ssdp
port is 1900 but I'm also runing a media server which listens on the same port.
So I get a conflict. May I change the basedriver port w
Hello all,
Can anybody please explain me the meaning of the
etc/org.apache.servicemix.management.cfg serviceUrl property
etc/management.properties com.sun.management.jmxremote.port property
and how should I configure them in server and client servicemix installations
in order to be able to open
I've attached my example project. To build it just run 'mvn install'.
To run it from the command line, run 'RunFooFromOsgi'. To run it within
Eclipse, import the project, then run fooOsgi. RunFooFromMain (command
line) and fooMain (Eclipse) run the example service provider
successfully outside
On 5/18/09 4:04 PM, Moloney, Tim M wrote:
I've attached my example project. To build it just run 'mvn install'.
To run it from the command line, run 'RunFooFromOsgi'. To run it within
Eclipse, import the project, then run fooOsgi. RunFooFromMain (command
line) and fooMain (Eclipse) run the exa
Tim,
I see you are using DynamicImport-Package to force visibility of the
implementation class by the FooFactory in the API bundle.
This is very dangerous. Your API bundle is going out and finding
exported classes from ANY bundle which happen to implement the Foo
interface as listed in the META-I
I agree that OSGi services solve this problem more cleanly than ServiceLoader.
Let me explain what I'm trying to do. We have code that needs to work in
several different frameworks or no framework at all. I am trying to create an
abstraction layer so that our code doesn't know the specifics o
Tim,
Maybe your should check out the peaberry project.
http://code.google.com/p/peaberry/
It is service layer agnostic and already comes with implementations for OSGi and
Eclipse. All you need to do is implement ServiceRegistry for your "stand alone"
use case and maybe you could reuse your Ser
10 matches
Mail list logo
