where ClassLoader can be passed in for OSGi.
Regarding bundle structure, I've restructured the layout here (so you don't
need to delete Groovy config):
https://github.com/pfirmstone/JGDMS/tree/Maven_build/modularize/JGDMS
The full commit history has been retained, so u can see all changes.
Cheers
Thanks Bharath, welcome to Apache River!
Interesting, are you able to create an OSGi support task on Jira and upload a
patch?
Cheers,
Peter.
Sent from my Samsung device.
Include original message
Original message
From: Bharath Kumar <bharathkuma...@gmail.com>
Sent: 20/01/2
Hello all,
I am Bharath kumar and this is my first mail to this group. I am following
River framework for the last 8 years. I have been using OSGi framework for
the past 7 years in various projects.
I made lot of attempts to use jini with OSGi framework.
Recently I got some success using River
Thanks Nic & Richard, will follow up your leads.
Peter.
Sent from my Samsung device.
Include original message
Original message
From: Niclas Hedhman <nic...@hedhman.org>
Sent: 18/01/2017 08:34:11 pm
To: dev@river.apache.org
Subject: Re: OSGi
Also, I am still on this lis
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
Peter,
If you have any general OSGi queries try the osgi-dev mail list - the folks
there are very willing to help with general OSGi questions. The link is
https://mail.osgi.org/mailman/listinfo/osgi-dev
<https://mail.osgi.org/mailman/listinfo/osgi-dev>
Best Wishes
Richard
>
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
201 - 207 of 207 matches
Mail list logo
