Re: [Architecture] Payload Factory improvements for JSON transformations
On Wed, Oct 9, 2013 at 12:00 PM, Ravi Undupitiya wrote: > We managed to get these scenarios working, the only limitations were the > ones due to the way Jettison handles anonymous classes. > > We're going to test generic json-path evaluator by giving the property > mediator ability to evaluate json-path. > > +1. Lets try to do the same approach as we do with stream xpath for json path as well. - For non-content-ware scenarios, we can use the PT pipe - For content aware scenarios, we should be able to use JSON Stream as we have enabled streaming builders and formatters. > > > > > > On Tue, Oct 8, 2013 at 5:31 PM, Kasun Indrasiri wrote: > >> Hi, >> >> We have been using PF for JSON based RESTful integration and there seems >> to have several areas to improve. >> >> - JSON->JSON - This works fine with JSON Path[1].. but we have to use >> JSON streaming builders/formatters. >> - XML-> JSON - This is not supported with JSON streaming builder, but >> have to switch to normal builder. Also there are some limitation on this >> due to Jettison limitations. >> - JSON-XML - Works fine. >> >> So, we have to get all these scenarios working for streaming builders and >> formatters. Ideally, we should made it the default builder and all other >> mediators should leverage the json-path functionality as an extension to >> expression (we have done this for Payload Factory). >> >> [1] https://code.google.com/p/json-path/ >> >> >> >> -- >> Kasun Indrasiri >> Software Architect >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 77 556 5206 >> Blog : http://kasunpanorama.blogspot.com/ >> > > > > -- > *Ravi Undupitiya* > Software Engineer; WSO2 Inc.; http://wso2.com > * > * > *E-mail: r...@wso2.com > **M: **+94 772 930 712* > * > *Lean . Enterprise . Middleware > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/ ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Payload Factory improvements for JSON transformations
We managed to get these scenarios working, the only limitations were the ones due to the way Jettison handles anonymous classes. We're going to test generic json-path evaluator by giving the property mediator ability to evaluate json-path. On Tue, Oct 8, 2013 at 5:31 PM, Kasun Indrasiri wrote: > Hi, > > We have been using PF for JSON based RESTful integration and there seems > to have several areas to improve. > > - JSON->JSON - This works fine with JSON Path[1].. but we have to use JSON > streaming builders/formatters. > - XML-> JSON - This is not supported with JSON streaming builder, but have > to switch to normal builder. Also there are some limitation on this due to > Jettison limitations. > - JSON-XML - Works fine. > > So, we have to get all these scenarios working for streaming builders and > formatters. Ideally, we should made it the default builder and all other > mediators should leverage the json-path functionality as an extension to > expression (we have done this for Payload Factory). > > [1] https://code.google.com/p/json-path/ > > > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com * * *E-mail: r...@wso2.com **M: **+94 772 930 712* * *Lean . Enterprise . Middleware ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Payload Factory improvements for JSON transformations
Hi, We have been using PF for JSON based RESTful integration and there seems to have several areas to improve. - JSON->JSON - This works fine with JSON Path[1].. but we have to use JSON streaming builders/formatters. - XML-> JSON - This is not supported with JSON streaming builder, but have to switch to normal builder. Also there are some limitation on this due to Jettison limitations. - JSON-XML - Works fine. So, we have to get all these scenarios working for streaming builders and formatters. Ideally, we should made it the default builder and all other mediators should leverage the json-path functionality as an extension to expression (we have done this for Payload Factory). [1] https://code.google.com/p/json-path/ -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/ ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
