Exactly :-). Data mapper is a mediator on its own and you can put it wherever you want.
Sanjiva. On Sat, Jul 20, 2013 at 7:15 AM, Samisa Abeysinghe <[email protected]> wrote: > After going though the initial design we came up with again, I think I got > it. > > Data mapper is on its own in the sequence, and not within other mediators. > I was trying to map the incoming and outgoing message through a mediator to > data mapper functionality. > > > On Fri, Jul 19, 2013 at 8:21 AM, Jasintha Dasanayake <[email protected]>wrote: > >> >> >> >> On Fri, Jul 19, 2013 at 4:21 AM, Samisa Abeysinghe <[email protected]>wrote: >> >>> >>> >>> >>> On Thu, Jul 18, 2013 at 10:52 PM, Sanjiva Weerawarana >>> <[email protected]>wrote: >>> >>>> On Thu, Jul 18, 2013 at 8:13 PM, Samisa Abeysinghe <[email protected]>wrote: >>>> >>>>> Yes it does. I was initially thinking of this the other way around, >>>>> when I was looking at the current visual tool and the way we can map the >>>>> current mediators to the visual data mapping aspect. >>>>> >>>>> What still concerns me is that, it sounds to me as if, we are >>>>> replacing the many mediators with one generic mediator. >>>>> >>>> >>>> No we're not at all .. *ALL* current mediators will remain. From the >>>> current visual tool perspective we're adding ONE new mediator: data mapper >>>> mediator. If you click on it, you will get a new visual editor opening up >>>> allowing you to define the input type (or it'll show it if its figured it >>>> out), the output type and allow you to visually map one to another. >>>> >>>> The alternative view I had was that, for all mediators, where there is >>>>> mapping between incoming format to outgoing format, we use a visual >>>>> mapper. >>>>> We (the tooling team) even had a place holder for the mapper against a >>>>> mediator and a model to let the developer "try-it". >>>>> >>>> >>>> There's no concept of input format / output format for generic >>>> mediators .. I don't think I understand what you're saying. >>>> >>> >>> OK, my perception came from a demo of a tool done by the tooling team. >>> We will arrange a demo and we will clarify. >>> >> >> What we have demo was same thing that is X studio's data mapping >> mediator, sure will do another demo >> >> /Jasintha >> >> >>> >>> Anyway, what I have seen, can be done with the data mapping mediator. >>> >>> >>>> Sanjiva. >>>> -- >>>> Sanjiva Weerawarana, Ph.D. >>>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >>>> email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880| +1 >>>> 650 265 8311 >>>> blog: http://sanjiva.weerawarana.org/ >>>> >>>> Lean . Enterprise . Middleware >>>> >>> >>> >>> >>> -- >>> >>> Thanks, >>> Samisa... >>> >>> Samisa Abeysinghe >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com >>> http://wso2.org >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Jasintha Dasanayake >> **Software Engineer >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware* >> * >> * >> *mobile :- 077 291 6596* >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
