A partner recently provided a useful HTTP-based API for me at short notice.
The API returned simple JSON representations of the current state of various events they had periodically ingested from our REST APIs.
A decision they made was to use
"no" values in the response, rather than booleans e.g.
1 2 3 4 5 6
I had written a Spring Social-based API client to interact with their API but wanted to deserialize their API response representation into a POJO that followed Java convention.Read on →