[
https://issues.apache.org/jira/browse/SHINDIG-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640498#action_12640498
]
Ian Boston commented on SHINDIG-656:
------------------------------------
Although fixing this is probably correct. I have 2 questions before I commit.
If lists were not handled, how was the SocialAPI working at all for JSON ?
I cant remember which part of the social api needed a list as a base container,
it must be there somewhere... what I missing ?
Also,
The Existing JSON Bean appears to have a number of shortcomings that the
community is providing patches for, is it time to switch to the net.sf json lib
version, that I think does all of this already ?
> 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.
