Presto.extjs.ServiceStore API or Example Doing Pagination w/ Registered REST
Hi,
I wanted get some clarifications before I respond back with a solution:
1) Do you have registered a REST service that already takes a start and end parameters ? Eg: myservice?start=0&end=20
In this case, the pagination is handled at the target service (outside of Presto) and all you have to do is to pass the start and end parameters, yes ?
2) For Presto to handle pagination, we require that the REST Service be wrapped in a Mashup first. To do this, you can create simple wrapper using Wires. Add your REST service in the Wires Canvas and wire the output of this block to the output of the Mashup. Save the Mashup as say "MyRESTService_Wrapper" and you can invoke this newly created wrapper instead of the REST service.
Let me know which one of these explains your situation better.
Thanks,
Kishore
Thanks for the comment and the criticism. I'd really like to get a little more information on where you have had problems with the documentation, so that we can do better.
Please email me at sara@jackbe.com if you have some time for a few questions.
Sara, technical writer/jackbe
1) Yes. The pagination is handled by the REST service. This is the situation that an example of the JavaScript using ServiceStore would be useful.
2) This would be helpful as well, although I currently do not have the need for it.
If there is an API for ServiceStore, I don't think an example was necessary. Can you point one to me and/or show an example?
I have seen that this is an example using the Presto.extjs.ServiceStore to populate information from a registered service, but it is an example specifically tailored to a SOAP service that brings back all the data. Even Ext seems to acknowledge that when calling service, the more common desire is to have server-side pagination. Can someone provide a working example on how this is done? I'm using a registered REST service that uses URL parameters to state the starting point and the number of results to return.
Just a constructive criticism, I'm a newbie and I have been impressed with what I've been able to get working. The problem is that the documentation is poor (incomplete, unorganized, not up-to-date, etc.), and that's been my commentary to others. I even have access to some JackBe consultants and they can't answer simple questions on how does the Presto Ext API work.