Also, I am still on this list, and can aid with answering question in details, but not really to put in hours to do the actual work.
The maven-bnd-plugin does most things right, but there is always a question of hiding internal packages/classes. Instead of aiming for running 'naked' on a blank OSGi container, I think it is generally better to start out with something like Apache Karaf. It will provide a lot for relatively little, incl so called wrapping of JARs into Bundles, provided by Pax URL[1] project, which also provides URL references of various kinds for many things. So, even if not going with Karaf, take a look at Pax URL. And in River, there is likely to be classloading issues, and although "Dynamic-ImportPackage" is available as a last resort, it should be avoided. Almost always the context classloader is a "mess", and there is a tendency of memory leaks when it is involved. [1] https://ops4j1.jira.com/wiki/display/paxurl/Pax+URL On Wed, Jan 18, 2017 at 11:18 AM, Peter Firmstone < peter.firmst...@zeus.net.au> wrote: > Any OSGi veterans willing to assist with JGDMS support for OSGi during the > modular restructure? > > I've added OSGi manifests to modules, but I also need to add classpath > manifest entry's for non osgi application compatibility, I'm using the > bnd-maven-plugin to generate the OSGi manifests. > > I also want to enable using ServiceLoader mediator manifest entry's for > OSGi, as the use of service provider style abstractions within River are > widespread. > > River also has its own service provider lookup mechanism: > org.apache.resources.Service > > Then there's the use of context ClassLoader's throughout to consider. > > Regards, > > Peter. > > Sent from my Samsung device. > > -- Niclas Hedhman, Software Developer http://polygene.apache.org <http://zest.apache.org> - New Energy for Java
