Sure. See http://blog.springsource.com/2009/01/19/exposing-the-boot-classpath-in-osgi/
for an in depth discussion by Costin of SS.
On Aug 19, 2009, at 12:08 PM, Michael Furtak wrote:
Hi Hal,
Thanks very much for your reply. I’m heartened that you’re confident
in this possibility. Is there any documentation for the option you
mention that I can refer to?
Thanks,
-Mike
THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS
ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you
are not the intended recipient, your use of this message for any
purpose is strictly prohibited. If you have received this
communication in error, please delete the message and notify the
sender so that we may correct our records.
From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org
] On Behalf Of Hal Hildebrand
Sent: Wednesday, August 19, 2009 3:01 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Bridging the plain Java and OSGi
classloading worlds
sure, you just have to have a class loader in common. The way this
would work is to modify the exports of the System bundle (an option
when starting the framework in Equinox) to export the classes from
the base class path you need. Then there is no class loader issues,
as they're both using the same.
On Aug 19, 2009, at 11:56 AM, Michael Furtak wrote:
Hi all,
I am using the EclipseStarter.startup(…) method to bring up the
Equninox framework from within a plain ol’ Java application. My
question is this:
Is it possible to allow the plain ol’ Java environment to get and
call service objects from the OSGi side? I know their respective
classloader environments are disjoint, but is there any hope at all
of bridging them? Has anyone been dumb/crazy enough to want to do
this?
Thanks,
-Mike
THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS
ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED,
CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you
are not the intended recipient, your use of this message for any
purpose is strictly prohibited. If you have received this
communication in error, please delete the message and notify the
sender so that we may correct our records.
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/equinox-dev
