Hi,
On Tue, Apr 8, 2014 at 10:38 AM, Gayan Yalpathwala <[email protected]> wrote: > Hi, > > Please find comments inline. > > > On Tue, Apr 8, 2014 at 9:51 AM, Asanka Sanjeewa <[email protected]> wrote: > >> Hi, >> >> Please see my comments in line. >> >> >> On Tue, Apr 8, 2014 at 7:25 AM, Lali Devamanthri <[email protected]> wrote: >> >>> >>> >>> >>> On Mon, Apr 7, 2014 at 11:36 PM, Viraj Rajaguru <[email protected]> wrote: >>> >>>> >>>> >>>> >>>> On Mon, Apr 7, 2014 at 9:54 PM, Selvaratnam Uthaiyashankar < >>>> [email protected]> wrote: >>>> >>>>> >>>>> >>>>> >>>>> On Mon, Apr 7, 2014 at 7:04 PM, Sohani Weerasinghe <[email protected]>wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> Please find the below mentioned points which discussed at the meeting >>>>>> held on 07/04/2014 regarding Visual DataMapper. >>>>>> >>>>>> *Participants*: Isabelle, Shankar, Srinath, Jasintha, Viraj, >>>>>> Susinda, AsankaS, GayanK, Lali, Sohani >>>>>> >>>>>> *Points :* >>>>>> >>>>>> - Data Mapper Mediator should have two extra properties to get >>>>>> the user defined input and output data format/type. >>>>>> - Instead of using message formatters, the data type/format >>>>>> conversion should be implemented inside the data mapper mediator and >>>>>> this >>>>>> can be done using Datum Writers and Readers Avro itself. >>>>>> - If the user didn't mention the data type, use JSON as the >>>>>> default data type. >>>>>> >>>>>> >>>>> Default data type should be same as incoming message type, isn't it? >>>>> we can get message type from message context. >>>>> >>>> >>>> Yes. We can get the message type from the message context and set it as >>>> the default data type. But we have to support for all the data types in >>>> data mapper mediator to do that. As the initial step we can define set of >>>> data type that are supported by Data Mapper mediator and set one of those >>>> data types as the default one (Eg:JSON). Will this work? >>>> >>>> What if delegate type conversion to another mediator rather than Data >>> Mapper mediator? Then Data Mapper mediator can return result from data >>> mapper engine and we can introduce type conversion mediators with >>> requirements. >>> >> >> Rather introducing another mediator for type conversion we can do the >> same thing within the Data Mapper Mediator itself as per discussed and >> decided during the meeting. So the data mapper mediator will map data using >> the data mapper engine and it will do the type conversion and output the >> payload as formatted payload according to the user defined output type. >> > +1 for proceeding with what we decided in meeting. IMO we have more control over with new mediator. >> >>> >>> Thanks, >>> Lali >>> >>>> >>>> Thanks, >>>> Viraj. >>>> >>>>> >>>>> >>>>> >>>>>> >>>>>> - User should have the ability to define the input and output >>>>>> Avro Schemas which needed. >>>>>> - When doing the data mapping, make the process more simple by >>>>>> letting the user only to create a project which automatically creates >>>>>> the >>>>>> Maven Multi Module Project, ESB Project and Registry Resource Project. >>>>>> >>>>>> In a glimpse, currently the user is supposed to create a Maven Multi > Module project and then create an ESB Config project inside that to create > a proxy service. In this proxy service, user is allowed to add a > data-mapper mediator like we do with other mediators. However, in order to > store data-mapper artifacts, user is forced to create or point to an > existing Registry resources project in the workspace in this process. > > As suggested by Isabelle, the above process can be automated from the > point a user clicks 'Map data' link in the dashboard, by creating all three > kinds of projects for the user automatically. The discussion was to > automate other artifact creation processes across developer-studio too > considering UX aspects. Although this is not technically impossible, IMO, > this kind of decision needs major changes in developer-studio flows that we > have been following until now. What kind of discussion should have on this? > > >>>>>> >>>>>> Thanks and Regards, >>>>>> Sohani >>>>>> >>>>>> >>>>>> Sohani Weerasinghe >>>>>> Software Engineer >>>>>> WSO2, Inc: http://wso2.com >>>>>> >>>>>> Mobile : +94 716439774 >>>>>> Blog :http://christinetechtips.blogspot.com/ >>>>>> Twitter : https://twitter.com/sohanichristine >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> S.Uthaiyashankar >>>>> VP Engineering >>>>> WSO2 Inc. >>>>> http://wso2.com/ - "lean . enterprise . middleware" >>>>> >>>>> Phone: +94 714897591 >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Viraj Rajaguru >>>> Software Engineer >>>> WSO2 Inc. : http://wso2.com >>>> >>>> Mobile: +94 77 3683068 >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Lali Sudaththa Devamanthri* >>> Software Engineer >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: +94 71 895 4922 >>> <http://www.wso2.com> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Asanka Sanjeewa* >> Senior Software Engineer >> Mobile: +94772532924 >> WSO2 Inc. http://wso2.com/ >> Blog: http://asanka-tech-blog.blogspot.com/ >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > Thanks, > > -- > *Gayan Kaushalya Yalpathwala* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 71 8682704 <http://asia14.wso2con.com/> > > <http://asia14.wso2con.com/> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Lali Sudaththa Devamanthri* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 71 895 4922 <http://www.wso2.com>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
