Hi, Ziv
Following are two sample requests:
1) curl -H Content-Type=application/json --data-binary
'{context:{container:"default"},
gadgets:[{url:"http://www.google.com/ig/modules/datetime_v2/datetime_v2.xml";,
language:"en", country:"US"}]}' shindig_metadata_service_url
Response:
{"gadgets":[{"errors":[null],"moduleId":0,"url":"http://www.google.com/ig/modules/datetime_v2/datetime_v2.xml"}]}
2) curl -H Content-Type=application/json --data-binary
'{context:{container:"default"},
gadgets:[{url:"http://www.google.com/ig/modules/todo.xml";,
language:"en", country:"US"}]}' shindig_metadata_service_url
Response is correct.
I did some simple tracing, and it seems that the problem is "view"
attribute of "content" element.
If you need any more information, let me know.
Thanks
Gerald
On Sun, Nov 7, 2010 at 7:01 PM, Ziv Horesh <[email protected]> wrote:
> Shindig metadata API is work in process, and I am not sure at what stage was
> it for the 2.0 cut.
> Can you attach an example request so I can take a look?
>
> Thanks
> Ziv
>
>
> On Fri, Nov 5, 2010 at 9:39 PM, Zhenhua Guo <[email protected]> wrote:
>
>> My code which uses shindig metadata API seems to be broken in shindig 2.0.
>> I found that if "Content" element has "view" attribute, the servlet
>> will return "{"gadgets":[{"errors" [null],"moduleId":0,"url":"url of
>> gadget"}]}".
>>
>> Thanks!
>>
>>
>> Gerald
>>
>
