+1 to standardizing Geode on Jackson for JSON processing. +1 to using JsonPath/json-path-assert for testing interactions in Geode on JSON docs.
On Thu, Sep 8, 2016 at 10:22 AM, Kirk Lund <kl...@apache.org> wrote: > Yes, we should change all json parsing code to use jackson. However, we > still need to write unit tests and that's what json-path-assert is for. > I've researched all of the ways to perform json assertions for unit tests > and test-path-assert is currently the best. It's from com.jayway same as > Awaitility. > > -Kirk > > > On Thu, Sep 8, 2016 at 10:06 AM, Jinmei Liao <jil...@pivotal.io> wrote: > > > Can we get rid of TypedJson in favor of some standard json libraries? > > > > On Thu, Sep 8, 2016 at 9:56 AM, Kirk Lund <kl...@apache.org> wrote: > > > > > To support fixing up unit tests that involve json, I'd like to add in a > > > dependency on com.jayway.jsonpath:json-path-assert. > > > > > > We already have a dependency on com.jayway.jsonpath:json-path (for > > > spring-hateoas). json-path-assert basically adds some new Hamcrest > > matchers > > > for clean assertions involving json. > > > > > > I intend to use this in TypedJsonJUnitTest (GEODE-1842) because that > > > test doesn't currently have assertions(!). > > > > > > -Kirk > > > > > > > > > > > -- > > Cheers > > > > Jinmei > > > -- -John 503-504-8657 john.blum10101 (skype)