felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From BJ Hargrave <hargr...@us.ibm.com>
Subject Re: OSGi, versioning and native code
Date Thu, 05 Jan 2006 13:38:21 GMT
Tim Ellison <t.p.ellison@gmail.com> wrote on 2006-01-05 05:39:57 AM:

> But in this example the "db2e" is not under version control, so multiple
> concurrently active versions of the "db2ejdbc" bundle are required to
> agree on a common db2e library.
> 
> Even if you put the db2e code into it's own bundle, you couldn't
> differentiate between the two versions when making a C call from db2jdbc
> to db2e (because you can't get a handle to the library version you want)
> unless you rely upon the loadLibrary() call to open the library for you.
> 
> I think the moral to this story is that the bundle versioning bottoms
> out at the loadLibrary() call, beyond that you should probably revert to
> deploying the platform libraries outside the framework, and using the
> platform's version control where it exists.

Probably wise. :-)

> 
> Regards,
> Tim
> 
> 
> -- 
> 
> Tim Ellison (t.p.ellison@gmail.com)
> IBM Java technology centre, UK.


Mime
View raw message