On Tue, Feb 16, 2016 at 11:17 AM, Jasintha Dasanayake <[email protected]> wrote:
> IMO , Both data mapper editor and the engine are a cross platform > components which can be used /ship with other product as well , Only the > ESB graphical mediator and synapse mediators should be added into exiting > ESB product and ESB tool repos , > Agree. Both editor and engine are cross platform components. > > Also I feel that it requires more frequent release in data mapper editor to > make it rock-solid also more new feature should be introduced to improve > the user experience ,therefore this editor should be able to release on its > own. > +1 for having two repositories for data mapper editor and engine. > > WDYT ? > > Thanks and Regards > /Jasintha > > > On Tue, Feb 16, 2016 at 10:11 AM, Chanaka Fernando <[email protected]> > wrote: > >> Hi Nuwan, >> >> +1 for keeping the Data mapper engine in a separate repo. That will make >> it easy to maintain and reuse by other components if there is a requirement >> in the future. >> >> >> On Tue, Feb 16, 2016 at 10:06 AM, Susinda Perera <[email protected]> >> wrote: >> >>> >>> >>> On Tue, Feb 16, 2016 at 10:01 AM, Nuwan Pallewela <[email protected]> >>> wrote: >>> >>>> >>>> Hi All, >>>> >>>> Data Mapper feature is planned to release with ESB 5.0 and initially it >>>> was done by team developer studio as a POC. >>>> >>>> There are three components in data mapper implementation. They are >>>> >>>> 1. Data Mapper Tool >>>> 2. Data Mapper Mediator >>>> 3. Data Mapper Engine >>>> >>>> Data Mapper Tool should be with the Developer Studio ESB Tooling. >>>> >>> This can also be place outside as this is a separate plugin. But ESB >>> plugin has a dependency to datamapper plugin. >>> >>>> Data Mapper Mediator should be move to Carbon Mediation. >>>> >>>> Ideally we should maintain a separate repository for the Data Mapper >>>> Engine. So where we should keep the Data Mapper Engine and how to proceed? >>>> >>> +1 for place this in a separate place, At the moment 'Data Mapper >>> Engine' is needed by datamapper-mediator, but datamapper-tool will also use >>> the engine (if we are giving some dry-run/emulator feature) >>> >>> Susinda >>> >>>> Thanks, >>>> >>>> Nuwan >>>> -- >>>> ---------------------------------------------------------- >>>> >>>> *Nuwan Chamara Pallewela* >>>> >>>> >>>> *Software Engineer* >>>> >>>> *WSO2, Inc. *http://wso2.com >>>> *lean . enterprise . middleware* >>>> >>>> Email *[email protected] <[email protected]>* >>>> Mobile *+94719079739 <%2B94719079739>@* >>>> >>>> >>>> >>> >>> >>> -- >>> *Susinda Perera* >>> Software Engineer >>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL) >>> Mobile:(+94)716049075 >>> Blog: susinda.blogspot.com >>> WSO2 Inc. http://wso2.com/ >>> Tel : 94 11 214 5345 Fax :94 11 2145300 >>> >>> >> >> >> -- >> Thank you and Best Regards, >> Chanaka Fernando >> Senior Technical Lead >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 773337238 >> Blog : http://soatutorials.blogspot.com >> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >> Twitter:https://twitter.com/chanakaudaya >> >> >> >> >> > > > -- > > *Jasintha Dasanayake* > > *Senior Software EngineerWSO2 Inc. | http://wso2.com > <http://wso2.com/>lean . enterprise . middleware* > > > *mobile :- 0711368118* > -- ---------------------------------------------------------- *Nuwan Chamara Pallewela* *Software Engineer* *WSO2, Inc. *http://wso2.com *lean . enterprise . middleware* Email *[email protected] <[email protected]>* Mobile *+94719079739@*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
