[ http://issues.apache.org/jira/browse/FELIX-28?page=comments#action_12444846 ] Richard S. Hall commented on FELIX-28: --------------------------------------
I have been prototyping require-bundle in my sandbox over the last few weeks. The approach I am taking is a three-step process: 1. Modifying the resolver algorithm to use a generic capability/requirement model (similar to the OBR2 model). 2. Modifying the consistency checking portion of the resolver algorithm to understand "bundle" capabilities. 3. Adding new type of wire for "bundle wires" in addition to the traditional "package wires". I have prototyped all three of these steps and believe that I have a workable approach. I have generated several example bundles to test the resolver and consistency checker and it appears to work. I have tested a simple set of bundles that actually load classed via required and re-exported packages. Now I need to try to apply these changes in a more polished and systematic way to the current trunk. Hopefully this can happen in a short time frame. The changes will likely be applied in two phases, step 1 will be applied first after it passes the TCK at the same level as the current framework. Then steps 2 & 3 will be applied next and hopefully these changes will get us further along with the TCK. > Implement require-bundle functionality > -------------------------------------- > > Key: FELIX-28 > URL: http://issues.apache.org/jira/browse/FELIX-28 > Project: Felix > Issue Type: New Feature > Components: Specification compliance, Framework > Reporter: Richard S. Hall > Assigned To: Richard S. Hall > > This issue is described in section 3.13 of the OSGi R4 specification. The > main jist is that bundles can now express explicit dependencies on other > named bundles. This means that the depending bundle imports everything that > the target bundle exports. It is also possible to re-export imported > packages. This issue impacts the resolver algorithm and will likely have some > impacts on the run-time class loading search order. -- 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
