-
Notifications
You must be signed in to change notification settings - Fork 40.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support non-blocking XML Marshalling with jackson-dataformat-xml #9581
Comments
Additional note, when using the routerfunction (webflux) the error is slightly different:
|
I guess you can't really compare with MVC and Boot 1.5 in that case; Could you create a Spring Framework issue and report back here once it's done? Thanks! |
Apologies, I just assumed the issue would be limited to Spring Boot - but it actually makes a lot of sense that it doesn't. I'll create the issue for Spring Framework and will keep you posted on the results here. |
Issue for Spring Framework created here: https://jira.spring.io/browse/SPR-15697 |
Excuse me, is there any update for this? |
@Clockwork-Muse It's blocked - waiting on FasterXML/jackson-dataformat-xml#260 |
what is work-around? |
Hi,
Jackson-xml marshalling seems to be broken in the 2.0.0 M2 milestone release for Spring boot (with web-flux). I tried both with functional web routers and a 'classic' (simple) annotation based controller (kotlin):
And
The jackson XML marshaller doesn't seem to be registered automatically anymore.
Steps to reproduce
jackson-dataformat-xml
dependency.Call the endpoint with the
application/xml
accept header. The sever will respond with a406 - not acceptable
response. In the logging this shows up:2017-06-23 12:39:42.629 ERROR 26064 --- [ctor-http-nio-2] o.s.w.s.h.ResponseStatusExceptionHandler : Response status 406 with reason "Could not find acceptable representation"
Verification
I've tried a similar approach with Spring Boot 1.5.4 and there it works as expected, depending on the provided accept header (
application/xml
orapplication/json
) the application responds with the response in the requested format.The text was updated successfully, but these errors were encountered: