For your and other's info...r-osgi is now available/distributed as part
of ECF remote services:
http://www.eclipse.org/ecf
It's one of several distribution providers that are supported by the ECF
remoting API, and contained within ECF's releases.
Actually, it sounds like inter-process communication/remoting may not be
perfect thing for your use case, but I thought I would clarify in any event.
Scott
Jae Woo Lee wrote:
Thank you for your response, Siamak.
Yes, an inter-process communication would work, but I am trying to
avoid it if possible. What I am trying to do is to build a network
router that supports plug-ins written in Java. I am using an existing
C-based router platform called Click and trying to put OSGi-based
plug-in architecture on top of it. I would like to try to have the
pieces work in a single process for performance.
Thanks for the pointer to R-OSGi. It seems a very useful thing in
general. I'll look into it further for any tip for JNI communications.
- Jae
On Apr 11, 2009, at 4:51 AM, Siamak Haschemi wrote:
Hello Jae,
I think the easiest way would be some kind of
Inter-Process-Communication. For example, the Apache Thrift library
should do it (there are many more). But you can also look at Jan
Rellermeyer work (R-OSGi). As far as I remember, he did something in
the area of communicating with C/C++ code (and the otherway around?).
Hope this helps.
- Siamak
Am 11.04.2009 um 08:11 schrieb Jae Woo Lee:
Hi,
I am using JNI Invocation API to start a JVM, which in turn starts
an Equinox container, which in turn loads my bundles.
I am having trouble trying to pass a piece of data from C code to a
bundle. When I try to "env->FindClass()" the Activator class in my
bundle, it fails. It's probably because the bundle is loaded from a
BundleClass loader rather than a system class loader.
Can anyone think of a way for me to pass some data from C code to
Java bundle code?
- Jae
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
