Hi,
Meeting notes from Data Mapping review.
1. Modify the current grammar
2. The current implementation of the Function executer should
not get the input file and execute it
3. Assuming the entire input stream is in memory does not
scale. Therefore that needs to be changed
4. The current implementation has omitted the root type, which
needs to be addressed
5. Multi value inner children are not taken into consideration
(ex: employee with multiple addresses)
6. Come up with a proper example
example: list of employees with multiple phone
numbers where each employee can has multiple phone numbers
The input will be XML file
The output will be in JASON file
Thanks.
On Fri, Aug 16, 2013 at 10:17 AM, Srinath Perera <[email protected]> wrote:
> Pls send the notes for yesterday discussion.
>
> --Srinath
>
>
> On Sat, Jul 20, 2013 at 12:48 PM, Susankha Nirmala <[email protected]>wrote:
>
>>
>>
>> On Saturday, July 20, 2013, Sanjiva Weerawarana <[email protected]> wrote:
>> > Exactly :-). Data mapper is a mediator on its own and you can put it
>> wherever you want.
>> Yes.we are working on that.user can put our data mapper mediator wherever
>> user want and then it generate avro schemas for input and output data
>> formates. User can done mapping according to that generated
>> schemas.According to the mapping done by user, it generate mapping
>> configuration.on the message flow, when message hit to data mapping
>> mediator, it execute mapping configuration and map input data to output
>> data.
>>
>>
>>
>>
>> > 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:
>>
>> --
>> 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
>>
>>
>
>
> --
> ============================
> Srinath Perera, Ph.D.
> http://people.apache.org/~hemapani/
> http://srinathsview.blogspot.com/
>
--
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
