+1 for Jackson. org.json was used because the developers of M&M responsible for this functional area using org.json decided it was an easier API to learn/use. As it turns out, org.json is too crude for most practical use cases.
On Thu, Dec 3, 2015 at 6:50 AM, Jens Deppe <[email protected]> wrote: > In the Geode codebase we currently make use of 2 different JSON libraries - > jackson is one and org.json is another. org.json has been included and > customized under the module gemfire-json. > > I'm curious as to why this is (if anyone knows). Before I submit a Jira, I > wanted to ask if anyone knows why we couldn't consolidate to a single JSON > library (I'd suggest jackson). > > Thanks > --Jens > -- -John 503-504-8657 john.blum10101 (skype)
