Hi Lali, I think we should stick to one convention, either traverse from input tree or traverse from output tree. We should not change the traversing side (input or output) considering the operator we got in the operator sequence path.
*option 1* We can start traversing from the input schema tree, when we got a operator we can search for all the input connections of that operator. And can traverse back using these input connectors. There can be connections from operators like Split, Concat and also operators like Constants. So that traversing logic will not miss operators like 'Constant' which has no any input. *option 2* Alternatively we can start traversing from output schema tree. So that we can traverse through all the operators including Constant, Split, Concat etc. But we will face the same problem one-day, if we get operators which has no any output in the operator sequence(I still cannot imagine a usecase). Thanks, Viraj. On Sun, Apr 27, 2014 at 1:40 PM, Lali Devamanthri <[email protected]> wrote: > Hi, > Configuration generation for mapping, handle with traversing in input > schema tree. If we consider the 'Constant operator' it may not connected to > input schema tree. Because of that, traversing only in input schema tree > would not enough for config generation. Shall we consider the traversing in > output schema for Constant operator (and similar operators)? > > Thanks, > /Lali > > -- > *Lali Sudaththa Devamanthri* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 71 895 4922 > <http://www.wso2.com> > -- 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
