[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Re: How to use launcher.jar in 3.3.0-M7?


Yes, because the equinox.launcher is still creating a separate classloader for the framework.  This is the classloader which the equinox.launcher is adding the osgi.framework.extensions to before launching the framework.  The option osgi.framework.ParentClassloader is only telling equinox.launcher what to use as the parent classloader of the framework classloader.

Tom



"Steven E. Harris" <seh@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

05/10/2007 04:13 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
equinox-dev@xxxxxxxxxxx
cc
Subject
[equinox-dev] Re: How to use launcher.jar in 3.3.0-M7?





Thomas Watson <tjwatson@xxxxxxxxxx> writes:

> Setting osgi.frameworkParentClassloader=current will set the
> framework's parent classloader to the same classloader which loaded
> org.eclipse.equinox.launcher.Main.  If you embed
> org.eclipse.equinox.launcher.Main into your application then you
> could use this option to get the same results.

In this "embedded launcher" scenario you describe with the
osgi.frameworkParentClassloader property set to "current", would the
launcher still be able to adjust the class path on its own to include
the framework extensions mentioned in the osgi.framework.extensions
property?

--
Steven E. Harris

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev