[
https://issues.apache.org/jira/browse/SHINDIG-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640507#action_12640507
]
Rodrigo Gallardo commented on SHINDIG-656:
------------------------------------------
> If lists were not handled, how was the SocialAPI working at all for JSON ?
Well, it was serializing OK, deserialization was the missing part.
AFAICT, deserializing json arrays is only used by shindig when reading a batch
json rpc request, and in that case the code explicitly tests for the string
being a "[ ... something ... ]" and does not call the BeanEncoder at all. I
only came across this because I tried to use the BeanEncoder to (de)serialize
my SPI objects to store them in memcached.
> Implement List decoding in BeanJsonConverter
> --------------------------------------------
>
> Key: SHINDIG-656
> URL: https://issues.apache.org/jira/browse/SHINDIG-656
> Project: Shindig
> Issue Type: Improvement
> Components: RESTful API (Java)
> Reporter: Rodrigo Gallardo
> Assignee: Ian Boston
> Priority: Minor
> Attachments: decode-json-array.patch
>
>
> Included patch implements requesting a json string to be decoded as a list.
> It assumes the string represents a json array, I simply could not find any
> reasonable way to handle a different case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
