Geek Answers Handbook

OSGi and legacy libraries

I watched OSGi for a while, and I wonder how best to work with the "old" libraries (released as simple JARs, not OSGi packages).

What do you think is the best way to handle this? By modifying their manifest file and adding minimal information about the node, then repackaging them is what I am doing at the moment, but it seems to me that something is wrong. Should I just use manual dependency management for these JARs (I do this for those libraries that are highly likely to be used only in a certain part of my application)?

As far as they are available, I use packages for Eclipse (since I use Equinox as the OSGi platform, this works well for those libraries that are available as packages).

Are there any repository packages other than Eclipse packages that I should be aware of?

+5
source share
2 answers

Spring comes OSGi heavily, using Equinox as its base platform.

http://www.springsource.org/dmserver

Rob Harrop's blog is worth keeping an eye on the evolution of OSGi.

And to answer your question, here's the Spring OSGi package repository:

http://www.springsource.com/repository/app/

+5
source

Eclipse Orbit, Eclipse. , , , , Jar as is Bundle-ClassPath: foo.jar. , foo.jar ( , Equinox), .

Spring , OSGi'ified.

+2

More articles:


All Articles