[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] extending the classpath of an embedded Framework
- From: Raymond Auge <raymond.auge@xxxxxxxxxxx>
- Date: Thu, 30 Aug 2012 00:23:47 -0400
- Delivered-to: email@example.com
In have an application with a large number of jars. Within that applicationÂI am initializing an embedded Framework instance.
Now, suppose I want to allow access to a subset of the packages available to the application which originate from the jars at hand (the actual osgi bundles deployed are mutually exclusive from the jars of the application).
In other words I'd like to effectively increase the classes available by building up a classpath of jars I want to expose as packages via the system bundle.
I built a mechanism (which I rather hate) which collects packages from a list of named jars, and passes this to the framework via the "org.osgi.framework.system.packages.extra" property. It's clunky and there has to be a better solution.
However, that property doesn't seem to exist anywhere in the juno source code, or it's use is so obfuscated that I can't find where it's might be, nor is it having any effect.
Am I making any sense?
Thoughts on how to handle this?
Raymond AugÃ Â|ÂSenior Software Architect |ÂLiferay, Inc.Â