+1 Chinthana. Our recommendation is to use camel case as we've done in carbon.xml. Product teams need to go through their configuration files and update where necessary.
But our options are very limited when it comes to updating config files coming from third party dependencies. Thanks, Sameera. On Tue, Jun 3, 2014 at 6:05 AM, Chintana Wilamuna <[email protected]> wrote: > Hi, > > There are a number of configuration files shipped with a product. These > files have inconsistent XML element naming. In some configuration files > entries use camel case (carbon.xml for example) in other configuration > files they capitalize the second letter of an entity (event-broker.xml). > > In a single file also there are some inconsistencies > <datasources-configuration>, <validationInterval>. > > Is it possible to follow a single convention when it comes to XML element > naming in config files? > > -Chintana > > -- > Chintana Wilamuna > Architect - Solutions Architecture > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > phone: +1 408 429 3321 > blog: http://engwar.com/ > photos: http://flickr.com/photos/chintana > linkedin: http://www.linkedin.com/in/engwar > twitter: twitter.com/std_err > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sameera Jayasoma, Software Architect, WSO2, Inc. (http://wso2.com) email: [email protected] blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
