On Mon, Jun 21, 2010 at 1:10 AM, Hiranya Jayathilaka <[email protected]>wrote:
> May be as a part of this impl we should introduce a new interface common to > all functional components of Synapse (mediators, sequences, endpoints, tasks > etc). Currently we have lot of common functionality distributed among > multiple interfaces (eg: setFileName, getFileName, getName). It would be > great to unify these stuff into a single interface. The documentation should > also be a part of this high level interface. WDYT? > > +1. I was thinking about introducing something like doucmentInclude. I think it is better to separate the file name in to a different interface. Thanks, Supun.. > Thanks, > Hiranya > > > On Mon, Jun 21, 2010 at 11:09 AM, Kasun Indrasiri <[email protected]>wrote: > >> >> +1 >> IMO, adding <documentation> tag is pretty straight forward than preserving >> the comments during building/serialization. >> >> -Kasun >> >> On Sun, Jun 20, 2010 at 11:53 PM, Supun Kamburugamuva >> <[email protected]>wrote: >> >>> Hi All, >>> >>> It is a good thing to facilitate documentation within the configuration >>> model it self. At the moment users can use XML comments. But when synapse >>> configuration model is built and serialized these XML comments get lost. So >>> it is better to have support for documentation comments. >>> >>> So one option is to add a documentation tag and a optional attribute to >>> the XML configuration elements to facilitate the documentations. Please add >>> your thoughts and comments. >>> >>> Thanks, >>> Supun.. >>> >>> >>> >>> >> >> >> -- >> Kasun Indrasiri >> Senior Software Engineer, >> WSO2 Inc. - "Lean . Enterprise . Middleware" - http://www.wso2.com/ >> Blog : http://kasunpanorama.blogspot.com/ >> >> > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -- Tech Lead, WSO2 Inc http://wso2.org supunk.blogspot.com
