一、场景
就是我们平常解析后台json字符串的时候,使用GSON类来解析,创建JavaBean的时候不要采用非静态内部类的方式,否则不小心会出现空指针的异常。看例子:
public class Boy {
public String boyName;
public Girl gril;
//非静态内部类
public class Girl {
public String girlName;
public String getBoyName() {
return boyName;//内部类获取外部类的变量
}
}
}
public class GsonError {
public static void main(String[] args) {
Gson gson = new Gson();
String boyJsonStr = "{\"boyName\":\"zhy\",\"gril\":{\"girlName\":\"lmj\"}}";
Boy boy = gson.fromJson(boyJsonStr, Boy.class);
System.out.println("boy name is = " + boy.boyName + " , girl name is = " + boy.gril.girlName);
System.out.println(boy.gril.getBoyName());//报错
}
}
结果如下:报错
boy name is = zhy , girl name is = lmj
Exception in thread "main" java.lang.NullPointerException
at com.kang.littleknowledge.javaDemo.model.Boy$Girl.getBoyName(Boy.java:16)
at com.kang.littleknowledge.javaDemo.GsonError.main(GsonError.java:17)
二、报错原因
Gson实际上内部在没有找到它认为合适的构造方法后,通过一种非常不安全的方式构建了一个对象。
public static UnsafeAllocator create() {
// try JVM
// public class Unsafe {
// public Object allocateInstance(Class<?> type);
// }
try {
Class<?> unsafeClass = Class.forName("sun.misc.Unsafe");
Field f = unsafeClass.getDeclaredField("theUnsafe");
f.setAccessible(true);
final Object unsafe = f.get(null);
final Method allocateInstance = unsafeClass.getMethod("allocateInstance", Class.class);
return new UnsafeAllocator() {
@Override
@SuppressWarnings("unchecked")
public <T> T newInstance(Class<T> c) throws Exception {
assertInstantiable(c);
return (T) allocateInstance.invoke(unsafe, c);
}
};
} catch (Exception ignored) {
}
// try dalvikvm, post-gingerbread use ObjectStreamClass
// try dalvikvm, pre-gingerbread , ObjectInputStream
}
其实最好的方式,会被Gson去做反序列化的这个model对象,尽可能不要去写非静态内部类。
三、解决办法
改成静态内部类,不能这样写,本来就不符合规范的写法