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
[json-serialize-action] does not work as intended #652
Comments
Should it be |
@oscerd @davsclaus what do you think ? |
I think so. Do we need this sorted for cutting the release again? |
would be nice, but I then don't know what to do with |
@nicolaferraro can you please shed some light on the serialize/deserialize configuration? |
Every time you use a data format / json etc then its like flipping a coin, if its marshal or unmarshal. |
yeah it should be unmarshal, when you want to jackson to bind data to POJOs when you use marshal then it takes "whatever" and writes that as an output stream (eg byte[] etc) |
2021-12-22 12:10:55.270 INFO 23227 --- [ - timer://tick] info : Exchange[ |
given that we have workaround now by using the json-serialize/deserialize action and that we may need to discuss the correct behavior a little bit more, I think we can start a release vote for 0.6 and leave this open. @oscerd @davsclaus what do you think ? |
+1 for releasing |
okay |
I have the following route that mimics what the json-serialize-action action is expected to do:
But when running it, the type of the body is
byte[]
instead of JsonNode:The text was updated successfully, but these errors were encountered: