Yes, I didn't want to say we need to apply that patch now. That patch should have being applied a long time ago :).
Thanks, Supun.. On Mon, Nov 9, 2009 at 11:52 AM, Hiranya Jayathilaka <[email protected]>wrote: > > > On Mon, Nov 9, 2009 at 11:51 AM, Supun Kamburugamuva <[email protected]>wrote: > >> https://issues.apache.org/jira/browse/SYNAPSE-458 >> >> It only implemented support for boolean properties. >> > > Thanks for pointing this out. But we should be able to do more than > that.... I'll create a new JIRA and link that to SYNAPSE-458. > > Thanks, > Hiranya > > >> >> Thanks, >> Supun.. >> >> On Mon, Nov 9, 2009 at 11:39 AM, Hiranya Jayathilaka < >> [email protected]> wrote: >> >>> >>> >>> On Mon, Nov 9, 2009 at 11:32 AM, Supun Kamburugamuva >>> <[email protected]>wrote: >>> >>>> +1, >>>> >>>> Actually there was a patch to property mediator implementing this same >>>> functionality. But I seemed nobody cared to look at it :) >>>> >>> >>> What's the JIRA please? Does it implement support for all the above >>> mentioned types? >>> >>> Thanks, >>> Hiranya >>> >>> >>>> >>>> Thanks, >>>> Supun.. >>>> >>>> >>>> On Mon, Nov 9, 2009 at 10:58 AM, Hiranya Jayathilaka < >>>> [email protected]> wrote: >>>> >>>>> Hi Folks, >>>>> >>>>> Currently the property mediator sets all property values as strings. >>>>> But in certain cases we will want to set property values of other types >>>>> (integers, floats, OMElement etc). For instance when using certain JMS >>>>> providers (eg: IBM MQ) this feature becomes a must, since they do not >>>>> allow >>>>> setting certain properties as strings. Such properties should be set with >>>>> specific types. >>>>> >>>>> To solve this problem I would like to propose adding a new attribute to >>>>> the property mediator. The new attribute, named 'type' will allow >>>>> specifying >>>>> a type for the parameter value. The property mediator will make sure that >>>>> the value is properly cast into the specified type before setting the >>>>> value. >>>>> If the attribute is not specified the default type 'string' will be used >>>>> so >>>>> the existing behavior won't be affected. >>>>> >>>>> I have already done this modificataion for WSO2 ESB. I have implemented >>>>> support for following types: >>>>> >>>>> - INTEGER >>>>> - FLOAT >>>>> - DOUBLE >>>>> - BOOLEAN >>>>> - LONG >>>>> - SHORT >>>>> - STRING >>>>> - OM (to set OMElement parameters) >>>>> >>>>> If there are no objections, I would like to contribute this improvement >>>>> to Synapse. So WDYT? Your comments and feedback are most appreciated. >>>>> >>>>> Thanks, >>>>> Hiranya >>>>> >>>>> -- >>>>> Hiranya Jayathilaka >>>>> Software Engineer; >>>>> WSO2 Inc.; http://wso2.org >>>>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>>>> Blog: http://techfeast-hiranya.blogspot.com >>>>> >>>> >>>> >>>> >>>> -- >>>> Software Engineer, WSO2 Inc >>>> http://wso2.org >>>> supunk.blogspot.com >>>> >>>> >>>> >>> >>> >>> -- >>> Hiranya Jayathilaka >>> Software Engineer; >>> WSO2 Inc.; http://wso2.org >>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>> Blog: http://techfeast-hiranya.blogspot.com >>> >> >> >> >> -- >> Software Engineer, WSO2 Inc >> http://wso2.org >> supunk.blogspot.com >> >> >> > > > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com
