Hello, I have done this when embedding the felix container in java based non-osgi aware (sort of) constructs and it's worked well -- a combo of the two below... extending to non-java should follow suit, seemingly; So, the conceptual drawback was if the exposed bundle API that I was using from the client code were to change, then I have some work to do, but that is to be expected in any case... I **think** I have some sample code lying around somewhere... Good luck, Craig Phillips, Praxis Engineering
________________________________ From: [email protected] on behalf of Jae Woo Lee Sent: Mon 4/13/2009 10:18 AM To: OSGi Developer Mail List Subject: Re: [osgi-dev] Communicating with a bundle from C code using JNI BJ and Stuart, I see. Moving the service interface out of the bundle and into the launcher classpath and adding it to the "extra" property will definitely work, and it's probably the cleanest solution. Reflection works too, but I don't want to add the overhead. For now I'm going the opposite route, namely have the launcher register a service and bundles import it. This satisfies my need. But it's good to know my options when I need to go the other way. Thank you again. - Jae _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
<<winmail.dat>>
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
