fixed JS mapping header serialization to string for array headers #2043
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes an issue about JavaScript mapping in Ditto connections which use Json arrays as value inside
headers
.Right now, this leads to e.g. the following follow-up exception (trying to parse
requested-acks
header as array):So arrays were not correctly serialized, but their
toString()
onNativeArray
(from Rhino library) was invoked, which just displays the defaulttoString()
implementation.This fix will transform the Rhino
NativeObject
andNativeArray
to ditto-jsonJsonObject
andJsonArray
and will use the buit-informatAsString()
for header values.