2.0.0

• Move from a custom JSON parser to GSON.

v1.0.3

Internal Change for Ticket 285:

Author: hlahlou

Changes made in Encoder and HttpClient to force the value for Content-Type to lowercase.

Added Unit Tests to ensure that deserialization and execution of HTTP request were case insensitive and could handle Content-Types of different casing (ex: application/json vs application/JSON)

Also updated the license, change log, and version to reflect changes made and to update copyright.

v1.0.2

This is related to a paypal existing bug, where the Java SDK can not deserialize certain response

where the customer input the given string in the request
"C/ Dinamarca "IPEX", 2"

And in order to send the string correctly, the SDK caller need to escape the special character,
the input string will have to be
"C/ Dinamarca \ \ \ "IPEX \ \ \ ", 2"

SDK will escape one backslash, and send the following to the API
"C/ Dinamarca \ "IPEX \ ", 2"

when the API successfully process the request, it will send
"C/ Dinamarca \ \ \ "IPEX \ \ \ ", 2 "

when we deserialize the JSON string, we are using the double quote as the ending indicator, However, it will fail if the responses contain a double quote that is supposed to be escaped, and thus only process "C/ Dinamarca \ \ \ " instead of the whole string.

Reference: #9

v1.0.1

Fixing a bug related to parsing integer from json

v1.0.0

Merge pull request #1 from tiffanyrzhou/master

case-fix