equinox

How to convert plugin.xml file to manifest.mf file as some tags like: <runtime> <library name="aaa.jar"> <export name="*"/> </library> <runtime> are seems to be ignored. Here is some correspondence in the next document, but far from complete reference. http://www.eclipse.org/eclipse/platform-core/runtime/adoption.html Open the file in the plugin.xml editor. On the Overview Tab>Plug-in Content section there should be a link, " ..., create an OSGi manifest " The OSGi manifest is a set of headers describing the bundle, the bundles or packages that are dependencies, and the packages this bundle

I'm just starting with OSGi and Eclipse RCP. Could someone explain to me the difference between "Eclipse" and "Equinox" as the target platform, when creating a new eclipse plugin project? I still know that Equinox is Eclipse's implementation of OSGi. I read in some articles that eclipse rcp is also based on Equinox. So where is the difference between the target platform you have to choose in a new Eclipse Plugin Project? Best regards It is about the environement in which the module you will be creating will run: see this Vogalla's RCP Tutorial Vogella's OSGi with Eclipse Equinox Eclipse

I have read a lot of equinox code for this, but still can't figure out a non-hacky way of getting the classloader for a osgi bundle in eclipse equinox setup. Is there one? The short answer (certainly for OSGi 4.1, not sure of 4.2) is you can't get a bundle's classloader. However the Bundle interface exposes a loadClass() method and this would allow you to write a classloader that wraps the bundle API and delegates to that loadClass() method. Or you can save some time and use Spring DM's BundleDelegatingClassLoader class instead. Balazs Zsoldos In OSGi 4.3 you can use: bundle.adapt(BundleWiring

I am pretty new to the whole Java and OSGi world and I have trouble understanding the eco system of a OSGi web application. To be more precise I am at the moment trying to understand how all the parts of the eco system are related to each other: OSGi Framework (e.g. Apache Felix, Equinox, Knoplerfish) OSGi Runtime (e.g. Spring DM Server, Pax Runner, Apache Karaf) Web Extender (e.g. Pax Web Extender, Spring Web Extender) Web Container (e.g. Apache Tomcat, Jetty) To give you a visual representation of my actual understanding of their relationship check out this image: As far as I know the OSGi

I've been using OSGi for a while now and I have various solutions to the problems I encountered. I wanted to revisit one of these and see if people had come up with different solutions. One of the most common issues I have with OSGi (Equinox 3.4.2) is the frequent unavailability of the Thread's context ClassLoader. I know this is partly an Equinox problem, but I have encountered the issue with Felix as well. I encounter this mostly with 3rd party libraries that start their own Threads or ThreadPools. When these are started during Bundle or DS activation, they can end up without their

I am trying to programatically start an OSGi framework (preferably Equinox) from Java and then load up any bundles. So I was going through this article which says how to do that. But I am getting java.util.NoSuchElementException everytime at the below line everytime ServiceLoader.load(FrameworkFactory.class).iterator().next(); Below is the code- import java.io.File; import java.util.HashMap; import java.util.LinkedHashMap; import java.util.Map; import java.util.ServiceLoader; import java.util.logging.Logger; import org.osgi.framework.Bundle; import org.osgi.framework.BundleContext; import org