Generally speaking when you serialize/deserialize an object, you are doing so to end up with an exact copy of the state of the object; As such, you generally want to circumvent the encapsulation normally desired in an OO design. If you do not circumvent the encapsulation, it may not be possible to end up with … Read more
Right now you are parsing the response as if it was formatted like this: { “contacts”: [ { .. } ] } The exception tells you this in that you are expecting an object at the root but the real data is actually an array. This means you need to change the type to be … Read more
Since they are private fields there should not be any problem while creating json string I don’t think this statement is true, GSON looks up at the object’s private fields when serializing, meaning all private fields of superclass are included, and when you have fields with same name it throws an error. If there’s any … Read more
Late to the party, but you can use a converter. RestAdapter restAdapter = new RestAdapter.Builder() .setEndpoint(“https://graph.facebook.com”) .setConverter(new DynamicJsonConverter()) // set your static class as converter here .build(); api = restAdapter.create(FacebookApi.class); Then you use a static class which implements retrofit’s Converter: static class DynamicJsonConverter implements Converter { @Override public Object fromBody(TypedInput typedInput, Type type) throws ConversionException … Read more
You’re telling Gson it’s looking for a list of maps of Strings to Objects, which essentially says for it to make a best guess as to the type of the Object. Since JSON doesn’t distinguish between integer and floating point fields Gson has to default to Float/Double for numeric fields. Gson is fundamentally built to … Read more
Moshi uses Okio to optimize a few things that Gson doesn’t. When reading field names, Moshi doesn’t have to allocate strings or do hash lookups. Moshi scans the input as a sequence of UTF-8 bytes, converting to Java chars lazily. For example, it never needs to convert integer literals to chars. The benefits of these … Read more
In my opinion, due to type erasure, the parser can’t fetch the real type T at runtime. One workaround would be to provide the class type as parameter to the method. Something like this works, there are certainly other possible workarounds but I find this one very clear and concise. public static <T> List<T> stringToArray(String … Read more
You can parse the JSONArray directly, don’t need to wrap your Post class with PostEntity one more time and don’t need new JSONObject().toString() either: Gson gson = new Gson(); String jsonOutput = “Your JSON String”; Type listType = new TypeToken<List<Post>>(){}.getType(); List<Post> posts = gson.fromJson(jsonOutput, listType);
Gson gson = new GsonBuilder() .setDateFormat(“yyyy-MM-dd’T’HH:mm:ss”) .create(); RestAdapter restAdapter = new RestAdapter.Builder() .setEndpoint(API_BASE_URL) .setConverter(new GsonConverter.create(gson)) .build(); Or the Kotlin equivalent: val gson = GsonBuilder().setDateFormat(“yyyy-MM-dd’T’HH:mm:ss”).create() RestAdapter restAdapter = Retrofit.Builder() .baseUrl(API_BASE_URL) .addConverterFactory(GsonConverterFactory.create(gson)) .build() .create(T::class.java) You can set your customized Gson parser to retrofit. More here: Retrofit Website Look at Ondreju’s response to see how to implement this … Read more
Since Gson 2.8.0, you can use TypeToken#getParameterized(Type rawType, Type… typeArguments) to create the TypeToken, then getType() should do the trick. For example: TypeToken.getParameterized(ArrayList.class, myClass).getType()