[ 
https://issues.apache.org/jira/browse/SHINDIG-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gary Helmling updated SHINDIG-60:
---------------------------------

    Attachment: fix-SHINDIG-60-bug_rome.patch

Since Eddie is licensed under the GPL (which wouldn't seem to allow use?), I've 
attached an alternate patch implemented using the ROME library 
(https://rome.dev.java.net/).  ROME is licensed under the Apache License, ver. 
2.  

This patch takes the same approach as the previous implementation, adding a 
dependency on ROME in the pom.xml, and returning the JSON object format 
specified in the Google Gadgets spec 
(http://code.google.com/apis/gadgets/docs/remote-content.html#Fetch_JSON) for 
the feed content.

One particular question I had was whether the "ErrorMsg" JSON property should 
be used to communicate errors (as the gadgets spec indicates), or a 
GadgetException should be thrown to be consistent with other Shindig handling.

> Shindig does not properly support the FEED content type as defined by the 
> gadgets spec for gadgets.io.MakeRequest
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-60
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-60
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Features (Javascript), Gadget Rendering Server (Java), 
> Gadget Rendering Server (PHP)
>            Reporter: Cassie Doll
>            Priority: Critical
>         Attachments: fix-SHINDIG-60-bug_rome.patch, io.js.patch, 
> ProxyHandler.java.patch
>
>
> The FEED contentType in gadgets.io.MakeRequest should not return general json 
> in the same way that the JSON contentType does. It should instead return a 
> structured object that looks like this: 
> http://code.google.com/apis/gadgets/docs/remote-content.html#Fetch_JSON

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to