[ http://issues.apache.org/jira/browse/FELIX-26?page=comments#action_12431237 ] Arnaud Quiblier commented on FELIX-26: --------------------------------------
IMHO: work done at 95% at least ... Modified sources & changelog can be found in the attached zip. Please carefull, revision I used to make changes may be obsolete now !! Here's the remaining details I'm not clear with: 1/ examining selected native code clause from bundle & attached fragments (R4, p.59, last but one paragraph) I think I should wait for fragment support. But can I do something right now ? open a sub-task, for example ? 2/ bundle must have required permission to load native code (R4, p.59, last paragraph) Idem as first remark. 3/ no matching clause but optional clause specified means no bundle installation error (p.61, middle) I return a 'null' path in this case, and this is the only one. But this method findLibrary() is called by a delegation of ClassLoaders, and I'm not sure to know how to prevent this bundle installation error. Any input welcome. 4/ loading of a native library file by multiple class loaders will result in a linkage error (R4, 3.9.2, p.63) Does this mean that we need a kind of lock system to prevent this multiple loading ? > Improve native library matching algorithm > ----------------------------------------- > > Key: FELIX-26 > URL: http://issues.apache.org/jira/browse/FELIX-26 > Project: Felix > Issue Type: Improvement > Components: Specification compliance, Framework > Reporter: Richard S. Hall > Attachments: 2006-08-29_FELIX-26_patch.zip > > > This issue is described in section 3.9 of the OSGi R4 specification. R4 has > improved and made the native library matching alogirithm; this is invoked > when a bundle's class loader is asked for the native library when a class in > the bundle has a native method. The current Felix implementation is a > simplified version of the OSGi R3 algorithm. This change should be localized > to the org.apache.felix.framework.OSGiLibrarySource class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
