Mybatis USES lazy step loading to cause json conversion exception
-
anomaly description
No serializer found for class org. Apache. Ibatis. Executor. Loader. The javassist. JavassistProxyFactory...
-
solve abnormal * * *
in distributed query each related bean class add annotation
@ JsonIgnoreProperties (value = {} "handler") -
reason
lazy loading is you have to use data will give you query 0, but 1 directly query object 2 into json string will lead to 3 results have not been query out of json4, This is what causes the interface 500 exception. Note : object does not load SQL query, only when output this object is use this data 0 will be 1 query 2 from the database and assign data to dependent object
3
4
5
Read More:
- 209151; org.json.JSONException A JSONObject text must begin with'{‘at character 1 of {
- com.fasterxml.jackson.databind.exc.InvalidDefinitionException: No serializer found for class
- Nuxt uses the image lazy to load the lazy component tag, and an error is reported
- Python’s json.loads Invalid control character
- Error attempting to get column ‘xxxxx’ from result set — after Lombok is annotated with builder, mybatis cannot recognize the correct type of field
- [jQuery] jQuery operates on JSON strings or JSON objects
- Error reporting when Lombok @ data and @ builder are used together
- Invalid object name ‘UserInfo’
- JSON and map convert to each other (using fastjson)
- Exception jsonmappingexception: out of start_ ARRAY token
- Error: required request body is missing, @ requestbody annotation usage
- Storing JSON data in session storage
- When websocket transmits JSON text, the parse method reports an error
- Spring MVC 406 status code / could not find acceptable representation
- Four ways to get Django parameters in request
- Getoutputstream() has already been called for this response
- Could not write JSON: write javaBean error, fastjson version x.x.x, class
- Solution of adding judgment error in the iterative process of Java iterator iterator
- @Controlleradvice exception [How to Solve]
- Qt development, using ODBC interface, query mysql, appear qsqlquery:: Value: not positioned on a valid record