The new system will show up in ESB as a mediator that can map from an input
type to an output type. So that means ANY ESB scenario can use this
mediator - its basically an alternative to the XSLT or XQuery mediators we
already have.

The ESB tool will integrate the data mapping tool via the data mapper
mediator.

So I think it does what you're describing?

Sanjiva.


On Thu, Jul 18, 2013 at 7:03 PM, Samisa Abeysinghe <[email protected]> wrote:

> Well, I was under the impression that this data mapping tool will help us
> with the mediators where we have i/p -> o/p data mapping use cases too.
>
> We have a common data mapping framework. So, for cases where the developer
> is using the visual tool, where there is format X to format Y mapping, can
> we not use this as the underlying framework and help the visual too do the
> mapping for the mediator functionality? Is that not the same use case for
> connector visual tooling?
>
>
> On Thu, Jul 18, 2013 at 6:06 PM, Sanjiva Weerawarana <[email protected]>wrote:
>
>> Sorry but I'm not getting it .. what's the connection to XSLT? I don't
>> think we should come close to XSLT in this .. we are going to have a new
>> mapper mediator that takes the config we are talking about and runs it
>> efficient (and streaming hopefully). We should NEVER replace that with the
>> XSLT one .. how does that make any sense for JSON-JSON for example? Even
>> for XML to XML what we're doing is much simpler - for simple cases. If you
>> want full XML transformation you always have the XSLT mediator - and that's
>> already there.
>>
>> Sanjiva.
>>
>> On Thu, Jul 18, 2013 at 8:17 AM, Srinath Perera <[email protected]> wrote:
>>
>>> Hi Samisa,
>>>
>>> Got it. How about adding WSO2 data mapper mediator  and start with that?
>>> Eventually that might replace XSLT one, but both should be around for some
>>> time.
>>>
>>> --Srinath
>>>
>>>
>>> On Thu, Jul 18, 2013 at 8:12 AM, Samisa Abeysinghe <[email protected]>wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Thu, Jul 18, 2013 at 8:04 AM, Srinath Perera <[email protected]>wrote:
>>>>
>>>>> I would say we start with our own
>>>>>
>>>>> IMO, XSLT is bit too complicated for first pass.
>>>>>
>>>>
>>>> Well, I am thinking mediators and the visual tool here and that is why
>>>> I keep saying XSLT :)
>>>> What other mediator we want to pick?
>>>>
>>>> I am keen to pick a mediator on the visual tool, so that we can design
>>>> the layout and the presentation strategy.
>>>>
>>>>
>>>>> --Srinath
>>>>>
>>>>>
>>>>> On Thu, Jul 18, 2013 at 5:29 AM, Samisa Abeysinghe <[email protected]>wrote:
>>>>>
>>>>>> Guys, please define a milestone plan for this too. What is the
>>>>>> mediator we will be using for the first POC? XSLT?
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 17, 2013 at 12:21 PM, Jasintha Dasanayake <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jul 15, 2013 at 6:40 PM, Samisa Abeysinghe 
>>>>>>> <[email protected]>wrote:
>>>>>>>
>>>>>>>> We are talking about the object model here - in other words the
>>>>>>>> underneath framework.
>>>>>>>>
>>>>>>>> Have we started investigating the visualization strategy on the
>>>>>>>> tooling front?
>>>>>>>>
>>>>>>>>      yes , we have done the investigation and figured out that GMF
>>>>>>> is the suitable technology for Visual part. As we agreed in the offline
>>>>>>> meeting (devS team and Samisa) both framework and Visual mapper will be
>>>>>>> developed parallelly
>>>>>>>
>>>>>>> /Jasintha
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jul 15, 2013 at 8:52 AM, Susankha Nirmala <
>>>>>>>> [email protected]> wrote:
>>>>>>>>
>>>>>>>>> Hi All,
>>>>>>>>>
>>>>>>>>> I have started working on $subject with Srinath.
>>>>>>>>>
>>>>>>>>> As we discussed, I have done a research of some data
>>>>>>>>> transformation technologies and architectures of them.
>>>>>>>>>
>>>>>>>>> 1) We assume all data types we map can be represented as a tree
>>>>>>>>> and accessed via a/b/c xpath like  format. For example, values in
>>>>>>>>> relational table we represented via one level paths.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2) We describe the mapping using a Avro like format. Let us take
>>>>>>>>> an example. Lets assume we need to convert following XML file to a 
>>>>>>>>> JSON
>>>>>>>>> document.
>>>>>>>>>
>>>>>>>>> <employee>
>>>>>>>>> <firstname>Susankha</firstname>
>>>>>>>>>  <lastname>Nirmala</lastname>
>>>>>>>>> <address>Street,123,State</address>
>>>>>>>>>  <dob>1985.10.31</dob>
>>>>>>>>> </employee>
>>>>>>>>>  We define the mapping using following Avro like format.
>>>>>>>>>
>>>>>>>>> mapping.json :
>>>>>>>>>
>>>>>>>>> {
>>>>>>>>>  fullName:concat($fname, $lname),
>>>>>>>>> Address{
>>>>>>>>>  address:
>>>>>>>>> {
>>>>>>>>>    "Street":"str.split($address, ",")[0]",
>>>>>>>>>    "Zip":"str.split($address, ',')[1]",
>>>>>>>>>   "State":"str.split($address, ',')[2]",
>>>>>>>>>  }
>>>>>>>>> "Age":"date.getAge($dob)"
>>>>>>>>>  }
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> Here str.split(..) date.getAge() are functions, and we pass
>>>>>>>>> reference to input document via xpath like paths starting with $.
>>>>>>>>>
>>>>>>>>> When we apply the mapping, the output will look like following. We
>>>>>>>>> will use defined path to travel the input file and extract values.
>>>>>>>>>
>>>>>>>>> {
>>>>>>>>> "fullname":"Susankha Nirmala",
>>>>>>>>>  "address":{
>>>>>>>>>  "Street": "Street",
>>>>>>>>>   "Zip": "123",
>>>>>>>>>   "State": "State"
>>>>>>>>>   }
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> Note, the output can be anything.  For example, it can be a
>>>>>>>>> database and we will auto map the structure define in mapping.config 
>>>>>>>>> to
>>>>>>>>> output type. (e.g. if output is a database, then it can only have one
>>>>>>>>> level).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> After Comparing this two schemas, Srinath and myself decided to
>>>>>>>>> use JSON for representing data mapping configuration. Also we decided 
>>>>>>>>> to
>>>>>>>>> use Jackson library for processing JSON configurations.
>>>>>>>>>  --Susankha and Srinath
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Susankha Nirmala
>>>>>>>>> Software Engineer
>>>>>>>>> WSO2, Inc.: http://wso2.com
>>>>>>>>> lean.enterprise.middleware
>>>>>>>>> Mobile : +94 77 593 2146
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ============================
>>>>> Srinath Perera, Ph.D.
>>>>>   Director, Research, WSO2 Inc.
>>>>>   Visiting Faculty, University of Moratuwa
>>>>>   Member, Apache Software Foundation
>>>>>   Research Scientist, Lanka Software Foundation
>>>>>   Blog: http://srinathsview.blogspot.com/
>>>>>   Photos: http://www.flickr.com/photos/hemapani/
>>>>>    Phone: 0772360902
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>
>>>
>>>
>>> --
>>> ============================
>>> Srinath Perera, Ph.D.
>>>   Director, Research, WSO2 Inc.
>>>   Visiting Faculty, University of Moratuwa
>>>   Member, Apache Software Foundation
>>>   Research Scientist, Lanka Software Foundation
>>>   Blog: http://srinathsview.blogspot.com/
>>>   Photos: http://www.flickr.com/photos/hemapani/
>>>    Phone: 0772360902
>>>
>>> _______________________________________________
>>> 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
>>
>
>
>
> --
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>



-- 
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

Reply via email to