SpringMVC3.2 resolves the data long accuracy loss problem when the PO returns to the foreground to JSON
Scheme
1. Customizing a Jackson JSON conversion class
Public classLongtostringadapterextendsObjectmapper {Private Static Final LongSerialversionuid = 4402127997078513582L; PublicLongtostringadapter () {Super(); Simplemodule Simplemodule=NewSimplemodule (); Simplemodule.addserializer (Long.class, tostringserializer.instance); Simplemodule.addserializer (Long.type, tostringserializer.instance); This. Registermodule (Simplemodule); }}
View Code
2, configure to the Springmvc file can be
<Mvc:annotation-drivenConversion-service= "Conversionservice"> <mvc:message-converters> <Beanclass= "Org.springframework.http.converter.json.MappingJackson2HttpMessageConverter"> < Propertyname= "Objectmapper"> <!--<bean class= "Com.fasterxml.jackson.databind.ObjectMapper" > - <Beanclass= "MyPackage." Longtostringadapter "> < Propertyname= "DateFormat"> <Beanclass= "Java.text.SimpleDateFormat"> <Constructor-argtype= "Java.lang.String"value= "Yyyy-mm-dd HH:mm:ss" /> </Bean> </ Property> </Bean> </ Property> </Bean> </mvc:message-converters> </Mvc:annotation-driven>
View Code
SpringMVC3.2 resolves the data long precision loss problem when the PO returns to JSON in the foreground