Hi all, Me and azeez started on the $subject before the Dec break. The latest code can be found here [1]
* Rationale and objectives: - there are so many bundles, even within carbon kernel and there seems to be unnecessary granularity. - In the future we are going to patch carbon kernel intead of kernel minor releases. - getting rid of not-so-kenel code. - this is the stepping stone to C5 efforts. * As of now: - identified few core modules - user.core, registry.core, caching, logging, datasources (but still user.core and registry.core depends on kernel..) - refactored the kernel, so that it only depends on registry,usercore and datasource api s. - carbon starts but having issues with admin services * to be done: - refactor user.core/registry.core to be independent of carbon kernel - we might need to change the user.api and registry.api while doing so. Right now these modules access tenant info using carbonContext. They don't get passed via API. - The UserRegistry implementation get used in modules. Not being an interface this creates coupling between modules. - remove implementation classes of user.core and registry.core and come up with simpleImpls. (may be in-memory ones) - Right now (after commenting out stuff), datasource components just registers datasources against JNDI. we have to think about a proper way of incorporating tenant datasources,replicating, etc. we need some help to complete above tasks. :) [1] https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/ thanks, --Pradeep
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
