|
Re: External libraries [message #125901 is a reply to message #125825] |
Tue, 17 February 2009 16:16 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: Dmitry.Negoda.gmail.com
Devasis Bassu wrote:
> Hi,
>
> I have a RCP application which provides a directory for end-users to
> provide libraries that they use (JDBC, JMS, etc. implementations). Some
> of my application plug-ins need to use those libraries at runtime.
>
> From what I understand about Equinox classloading, the simplest way
> would be create a manifest on the fly using full paths to all the
> external libraries and register the whole thing as a bundle. The extra
> step is to discover all the packages in the libs for exporting within
> the manifest.
>
> My questions are...
> 1) Does it matter which plug-in within my application does this dynamic
> bundle loading?
> 2) DynamicImport-Package: * has to added only to the plug-in(s) that
> would use these libraries?
> 3) Do I have to explicitly uninstall the dynamic bundle given that I
> need those libraries around as long as my application?
>
> Is this approach really the simplest solution?
It seems to me the better approach whould be to simply create another
ClassLoader, URLClassLoader for example, and use this class loader to
load JDBC/JMS implementation classes.
>
> Thanks,
> - Devasis
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02984 seconds