Skip to content
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 content response is serialized incorrectly when resource is set in the request URI #378

Closed
boria8 opened this issue Jul 3, 2018 · 0 comments
Labels

Comments

@boria8
Copy link

boria8 commented Jul 3, 2018

For example on reading reqest from /3/0/1 URI the client returns the following payload:
{"bn":"/3/0/1/","e":[{"n":"1","sv":"00000"}]}
The client serialize the payload as multi instance resource while the resource is of type string.

seems that json_serialize function should set rootLevel to URI_DEPTH_RESOURCE_INSTANCE only if tlvP->type==LWM2M_TYPE_MULTIPLE_RESOURCE

sbertin-telular added a commit to sbertin-telular/wakaama that referenced this issue Mar 12, 2019
Fix problem serializing resource instance reads.
Fix handling of empty strings and opaque.
Fix JSON serializing single instance resource as multiple. Fixes eclipse-wakaama#378.
Fix JSON parsing of multiple instance resources. Fixes eclipse-wakaama#399.

Signed-off-by: Scott Bertin <sbertin@telular.com>
@sbernard31 sbernard31 added the bug label Nov 3, 2020
sbertin-telular added a commit to sbertin-telular/wakaama that referenced this issue Nov 18, 2020
Fix problem serializing resource instance reads.
Fix handling of empty strings and opaque.
Fix JSON serializing single instance resource as multiple. Fixes eclipse-wakaama#378.
Fix JSON parsing of multiple instance resources. Fixes eclipse-wakaama#399.

Signed-off-by: Scott Bertin <sbertin@telular.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants