Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
Description
Original PR and conversation: https://github.com/resteasy/resteasy/pull/3030
This is a breaking change, it's probably a starting point. Probably a configuration is needed to opt-in for the feature.
Returning null here doesn't seem correct at all. Determining a way to reproduce this would be ideal to see what happens. Not having a media type in general seems like a bug.
If the server doesn't send the Content-Type header, the client gets null with no explanation. AFAIU, the only way to troubleshoot is debugging.
Per the documentation, the ResponseProcessingException might be the correct exception to throw.
Attachments
Issue Links
- is incorporated by
-
WFLY-17020 Upgrade RESTEasy to 6.2.0.Final
-
- Closed
-
-
WFLY-16865 Upgrade RESTEasy to 6.2.0.Beta1
-
- Closed
-