Folks, I had a look at the BAM code on the trunk (while fixing the maven structure, I had to :-) ), first of all it doesn't seem to be in sync with the branch or rest of the carbon trunk. I had to fix a few compilation errors.
Please note that some fixes are sort of hacks, just to get the code compiling, where a BAM person with a better understanding has to fix them properly. I put TODO comments on those places. Most importantly I see a lot of boiler plate code on the bam-data-publishers module, where we can abstract out most of them into a top level abstract class. By looking at the current BAM trunk, users who are writing a data publisher has to write a lot of unwanted code, well we could provide a basic impl of those and users could overwrite that if they want to change the behavior. I propose a code review of BAM soon after we start. WDYT? Thanks, Ruwan -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: [email protected]; cell: +94 77 341 3097 blog: http://blog.ruwan.org _______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
