Again, I am no big fan of the extclasspath extensions. They were added by the Equinox security team a long time ago when they needed to get access to things in the extension class path that were not allowed to be on the boot class path. So it was a similar issue as the JavaFX. The way they work is to change the class loader delegation of only the packages exported by the extension fragment. All other packages exported by the system bundle would use the normal class loader delegation as they do by default (i.e. simply use the class loader that loaded the framework implementation).
Unfortunately such a thing may be needed in the future to support normal system.bundle fragments if the framework implementation ends up being loaded by a modular class loader in Java 9 (or when ever Java Modularity is in the VM). Support today for system.bundle fragments is done by depending on the fact that the framework is typically loaded by a URLClassLoader and we can dynamically add more URLs to its class path. I don't expect a true modular class loader in Java 9 would allow us to do this. Tom From: Tom Schindl <[email protected]> To: [email protected], Date: 11/14/2012 06:06 AM Subject: Re: [equinox-dev] Equinox, PDE and packages from the ExtensionClasspath (e.g. JavaFX) Sent by: [email protected] Am 14.11.12 12:49, schrieb Neil Bartlett: > > > On Wed, Nov 14, 2012 at 11:34 AM, Tom Schindl > <[email protected] <mailto:[email protected]>> wrote: > > Am 14.11.12 08:13, schrieb Gunnar Wagenknecht: > > Am 14.11.2012 01:30, schrieb Neil Bartlett: > >> I really feel that the problem is in the launcher, so that's where it > >> needs to be fixed, i.e. by setting the osgi.parentClassloader=app > system > >> property. > > > > I agree. So the wrong property is only used if the Equinox is launched > > using the binary executable or also when launched using "java -jar > > org.eclipse.osgi..."? > > > > Please note that we can't simply change the launcher to use the > ext-classpath because then we'd most likely break other Eclipse plugins! > > > I really don't think so. I had a brief chat with Tom W about the reason > why Eclipse uses the boot loader as its parent. Apparently it dates back > to Eclipse 2.x (pre-OSGi) and conflicts with the Xerces XML parser that > was being shipped in Sun JREs around that time. You see the irony, I > hope.... back then it was necessary to avoid exposing Eclipse to non-JSR > libraries in the extension loader. Now we WANT to expose Eclipse to > non-JSR libraries in the extension loader. You can't have your cake and > eat it. > > Why not try running Eclipse right now with osgi.parentClassLoader=app, > and find out what happens? > I agree fully with you and see the irony and naturally the best would be that equinox would switch to the app classloader. I can try to run my stuff and some other eclipse plugins I'm using and in my daily work and most certainly they won't break but I'm not the one who can make the decision that Eclipse IDE (or better Equinox) has to switch to it by default. What I'm providing is a plugin for the Eclipse IDE and I'm not in control of this setting :-( > > We only change the classpath for a specific fragment. At least this is > how I interpreted Tom Watsons suggestion to use the above format. > > > I just don't see how it's possible for the framework to change its own > classpath for different fragments. Maybe Tom has some ideas. However I > think this solution could come with its own set of plugin breakages, if > it even works at all. > I'm not sure what is happening when I set this specific header in side my fragment, only Tom can answer that. Will it only switch the classloading of packages exported of this specific fragment? Will it switch the classloader for the complete system.bundle? I have no idea. Tom -- B e s t S o l u t i o n . a t EDV Systemhaus GmbH ------------------------------------------------------------------------ tom schindl geschäftsführer/CEO ------------------------------------------------------------------------ eduard-bodem-gasse 5-7/1 A-6020 innsbruck fax ++43 512 935833 http://www.BestSolution.at phone ++43 512 935834 _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
