Ah, I see. Actually, if you look carefully, Shindig is doing the right thing in javascript. The spec specifically says "When processed, returns an object whose "activities" property is a Collection<Activity> object." so is you do getData.activities, that should be a collection.
This is a relic from the 0.5 apis where there was also a "stream" property. So.. the spec is sorta weird, and should be fixed. But Shindig is doing the right thing in javascript. - Cassie On Wed, Apr 9, 2008 at 4:44 PM, Alejandro Rivero <[EMAIL PROTECTED]> wrote: > just to clarify; the problem is not that there is not paging, the real > problem is that neither .getData().each() nor .getData().size work > when the answer is a collection of activities, while they do work when > the request is for a collection of persons. > > 2008/4/9 Alejandro Rivero <[EMAIL PROTECTED]>: > > > > 2008/4/9 Cassie <[EMAIL PROTECTED]>: > > > > > > > So the Shindig java code is doing the right thing. > > > If we think activities should have paging, then someone should just > > > bring it up on the spec mailing list. > > > > > > - Cassie > > > > > > > Yep, it is doing the right thing. The bug is in the javascript side, I > > just sent a report. > > >
