[Home] [By Thread] [By Date] [Recent Entries]
I am working with a relatively simple interoperability scenario where I must consume health facilities from a health facility registry api (which churns out json), transform them into a different format and post them through to the api of another system. What makes this irritating is that I have to maintain a model of the health facility registry object which I have to unmarshall the json to, in order to transform it. I don't want these objects and I don't want to be unmarshalling anything. Thats extra code to maintain so, as ever, the simplicity catches up with you. I just want to transform the representation. With an xml source I have one xslt to maintain. With json I have both the code to unmarshall plus the code to transform.
Bob On 12 November 2013 14:16, Costello, Roger L. <costello@m...> wrote: I'll accept that JSON is a simple data design that makes easy programming tasks easier.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |

Cart



