Folks, We got carried away a bit when we adopted OSGi & started creating one OSGi bundle per top level package. So we ended up with 100s of bundles, and things have become unmanageable to a certain degree. We are going to fix that with Carbon 5 & we will end up with a much smaller number of bundles. For example, the screenshot below shows the Carbon kernel OSGi bundle which now includes a number of top level packages. I think it may even be a good idea to rename the bundle to carbon-kernel.jar instead of org.wso2.carbon.kernel.jar. We will need to adopt the same practice for components where we would have to merge a number of existing components. For example, I can think of mediators.jar & perhaps governance.jar.
[image: Inline image 1] Thoughts & suggestions about this approach are welcome. One concern would be that we won't be able to do fine-grained patching, but that is a compromise we are willing to make, and having a smaller number of bundles will make it easier to manage patches. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
<<Screen Shot 2013-03-13 at 6.50.25 AM.png>>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
