Hi Azeez, On Tue, Mar 8, 2011 at 8:52 PM, Afkham Azeez <[email protected]> wrote:
> > > On Tue, Mar 8, 2011 at 8:40 PM, Lahiru Gunathilake <[email protected]>wrote: > >> Hi Azeez, >> >> On Mon, Mar 7, 2011 at 7:11 PM, Afkham Azeez <[email protected]> wrote: >> >>> 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? >>> >> Yes this is for multiple instance config and the XML is aligned when I >> check with G-Reg pack. What Readme should these information have to go ? I >> don't see any place we explain all the files in repository/conf directory. >> > > repository/conf/README. > > Also, need to have header comments. Also, you need to explain each element > and its usage in the XML file itself. We have set an example by following > these practices in the carbon.xml file and some other files as well. > Sure will change it. Thanks a lot for pointing this out ! Lahiru > > >> >> Lahiru >> >>> >>> >>> >>> -- >>> *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 >>> >>> >> >> >> -- >> Lahiru Gunathilake >> Senior Software Engineer - WSO2 Inc. www.wso2.com >> >> Email:[email protected] Blog: www.lahiru.org >> Mobile: +94716381143 >> >> Lean . Enterprise . Middleware >> >> > > > -- > *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* > > -- Lahiru Gunathilake Senior Software Engineer - WSO2 Inc. www.wso2.com Email:[email protected] Blog: www.lahiru.org Mobile: +94716381143 Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
