Folks, We have too many conf files and it would be very confusing for a user. Perhaps we can merge some of these files. Also, it would be good if the header section of each file mentions the purpose of these files. This practice was followed when we defined the carbon.xml file, but the people who added the other files have not learnt from that.
jgroups-s3_ping-aws.xml - Senaka what is this file used for? JCache? Can we have this file elsewhere, or call it jcache-config or something? Why isn't it explained in the README? cache.xml - Senaka why isn't this in the README? Can't we merge this with the above file? broker-config.xml - Lahiru, Senaka, why isn't this in the README. ports-config.xml - Lahiru what is this file used for? Multiple instance config? Why isn't it explained in the README? Why isn't the XML aligned? -- *Afkham Azeez* Senior Software Architect & Senior Manager; 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*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
