You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Indeed, when I add the swagger dependency to my project the errors are not serialized normally by jackson
I am in a webflux project where I use problem-spring-webflux from version 0.27.0 to handle my errors, it is configured normally according to the github documentation (jackson configuration with ProblemModule and ConstraintViolationProblemModule...) and it works perfectly, my errors are handled perfectly. On the other hand I would like to expose my APIs which leads me to use springdoc-openapi-webflux-ui from version 1.6.7, and after that my errors with zalando are not serialized normally. no exceptions are raised in the code but the answers do not come correctly.
For a 401 error that was displayed normally, is displayed after installation of the swagger library as follows:
and without the swagger library it appears as follows
{
"type": "problem-with-message",
"title": "Unauthorized",
"status": 401,
"detail": "User string was not found in the database",
"path": "/api/authenticate",
"message": "error.http.401"
}
The text was updated successfully, but these errors were encountered:
Indeed, when I add the swagger dependency to my project the errors are not serialized normally by jackson
I am in a webflux project where I use problem-spring-webflux from version 0.27.0 to handle my errors, it is configured normally according to the github documentation (jackson configuration with ProblemModule and ConstraintViolationProblemModule...) and it works perfectly, my errors are handled perfectly. On the other hand I would like to expose my APIs which leads me to use springdoc-openapi-webflux-ui from version 1.6.7, and after that my errors with zalando are not serialized normally. no exceptions are raised in the code but the answers do not come correctly.
For a 401 error that was displayed normally, is displayed after installation of the swagger library as follows:
{
"cause": null,
"stackTrace": [
{
"classLoaderName": "app",
"moduleName": null,
"moduleVersion": null,
"methodName": "build",
"fileName": "ProblemBuilder.java",
"lineNumber": 83,
"className": "org.zalando.problem.ProblemBuilder",
"nativeMethod": false
},
{
"classLoaderName": null,
"moduleName": null,
"moduleVersion": null,
"methodName": "process",
"fileName": "ExceptionTranslator.java",
"lineNumber": 89,
"className": "com.jod.elio.gescom.web.rest.errors.ExceptionTranslator",
"nativeMethod": false
},
{
"classLoaderName": "app",
"moduleName": null,
"moduleVersion": null,
"methodName": "lambda$create$2",
"fileName": "AdviceTrait.java",
"lineNumber": 129,
"className": "org.zalando.problem.spring.webflux.advice.AdviceTrait",
"nativeMethod": false
},
{
"classLoaderName": "app",
"moduleName": null,
"moduleVersion": null,
"methodName": "onNext",
"fileName": "MonoFlatMap.java",
"lineNumber": 125,
"className": "reactor.core.publisher.MonoFlatMap$FlatMapMain",
"nativeMethod": false
},
...
}
and without the swagger library it appears as follows
{
"type": "problem-with-message",
"title": "Unauthorized",
"status": 401,
"detail": "User string was not found in the database",
"path": "/api/authenticate",
"message": "error.http.401"
}
The text was updated successfully, but these errors were encountered: