Just checked it now and ran the JS integration tests[1] and it's working. Perhaps the instance was "sleeping" due to inactivity and was starting up when you made the calls. Can you try again and verify that it is working now?

About the next link, you will always get a next link with the current impl. Previously we did not send a next link if there was no more data to be retrieved, but I think you brought up the case where new data might be added after the client's latest call. Without the next link the client will not have knowledge of the next page link. Instead, the result of call to the next page when no data exists will return an empty array. 

Bug or no bug, let me know what you would like to see here and we'll make it so :)

[1] http://aerogear.github.com/aerogear-js-integration/unit/pipeline/paging.html

Den måndagen den 1:e april 2013 skrev Kris Borchers:

Hey all,

Anyone know why I get a 404 from corscontroller-aerogear.rhcloud.com? JS is using that for paging integration tests but now it fails.

Also, I believe I may have found a bug in paging but not sure where I can test since that app is down. It appears I get a "next" link even where there isn't a next page so makes it hard to test if I should display a "next" link in the UI.
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev