Re: [Architecture] Introducing a Custom Mediator for Data Mapper

2014-04-07 Thread Lali Devamanthri
Hi, On Fri, Apr 4, 2014 at 11:09 AM, Gayan Yalpathwala gay...@wso2.com wrote: Hi Sohani, On Fri, Apr 4, 2014 at 10:44 AM, Sohani Weerasinghe soh...@wso2.comwrote: Hi, As I mentioned above the data mapper engine gives the output as JSON and the output format can be anything not only

Re: [Architecture] Introducing a Custom Mediator for Data Mapper

2014-04-07 Thread Malaka Silva
+1 this makes integration between connectors much simpler. (recipes) To begin we need to support XML, JSON and CSV On Tue, Apr 8, 2014 at 9:57 AM, Sohani Weerasinghe soh...@wso2.com wrote: Hi All, As per discussed the Data Mapper Mediator should aware about the data type/format given as

Re: [Architecture] Introducing a Custom Mediator for Data Mapper

2014-04-03 Thread Chanaka Fernando
Hi Sohani, +1 for the DataMapperMediator idea. If you could give another option to select the output format either as XML or JSON, that would be really helpful. WDYT? Thanks, Chanaka On Thu, Apr 3, 2014 at 6:32 PM, Sohani Weerasinghe soh...@wso2.com wrote: Hi, As per previous discussions

Re: [Architecture] Introducing a Custom Mediator for Data Mapper

2014-04-03 Thread Sohani Weerasinghe
Hi, As I mentioned above the data mapper engine gives the output as JSON and the output format can be anything not only JSON or XML. Therefore 'DataMapperMediator' needs to be implemented in such a way to have two properties for input and output types. Basically there can be a default format

Re: [Architecture] Introducing a Custom Mediator for Data Mapper

2014-04-03 Thread Gayan Yalpathwala
Hi Sohani, On Fri, Apr 4, 2014 at 10:44 AM, Sohani Weerasinghe soh...@wso2.com wrote: Hi, As I mentioned above the data mapper engine gives the output as JSON and the output format can be anything not only JSON or XML. Therefore 'DataMapperMediator' needs to be implemented in such a way to