Just to close the loop on this, I've made good progress prototyping bundles in our current system. Basically, I can achieve modularity by having a single manifest file for each existing jar, but having that manifest point to any number of independent XML files in its Service-Component attribute (I'm using Descriptive Services). Each XML file describes a component that exposes and/or uses a service.
The result is that each existing jar has to be loaded as a unit (bad), but in terms of the code itself, there is a loose coupling between components within that jar or across jars (good). -- View this message in context: http://www.nabble.com/non-jar-as-bundle-unit-tp15805581p16002323.html Sent from the Apache Felix - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
