We have had heated arguments about this before, and always ended up using plain old boring XML. So please go with XML. No need to do anything fancy.
Azeez On Tue, Nov 18, 2014 at 12:59 PM, Isuru Perera <[email protected]> wrote: > Hi, > > I'm working on a new component for metrics collection in WSO2 Platform [1]. > > I need to introduce a configuration file. In WSO2 products, most of the > configurations are in XML. There are some configurations in properties > files. > > In other projects, there is a trend to move away from XML and use other > formats like YAML [2]. > > Should I follow the convention in WSO2 components and use XML/properties? > or can I use any format like YAML? > > I haven't decided on the format or configuration options yet for my > component. I just want to know recommendations on introducing a > configuration file to WSO2 platform. > > Thanks! > > Best Regards, > > [1] http://markmail.org/message/gc6nixvzvibh7yxo > [2] http://www.yaml.org/ > > -- > Isuru Perera > Senior Software Engineer | WSO2, Inc. | http://wso2.com/ > Lean . Enterprise . Middleware > > about.me/chrishantha > -- *Afkham Azeez* Director of Architecture; 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 3320919blog: **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 <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
