topic Re: Repository Service: Batching of results in Alfresco Archive

Repository Service: Batching of results

marian — Fri, 02 Nov 2007 11:23:04 GMT

Hi,I am trying to batch results returned from a query. I have specified a QueryConfiguration header with a deliberately small fetchSize of 5. I still get all results returned, 52 rows in this case.This is the SOAP message sent:<?xml version="1.0"?><SOAP-ENV:Envelope xmlnsOAP-ENV="http://s

Re: Repository Service: Batching of results

marian — Fri, 02 Nov 2007 16:11:25 GMT

Update:

When I created the header as:

<QueryHeader><QueryConfiguration><fetchSize>5</fetchSize></QueryConfiguration></QueryHeader>
‍‍

The behaviour is the same

Re: Repository Service: Batching of results

mruflin — Mon, 05 Nov 2007 08:03:55 GMT

I'm experiencing exactly the same problem.

Can somebody please post a successful soap request that takes fetchSize into consideration? I'm trying to connect to Alfresco 2.0.1E.

Re: Repository Service: Batching of results

mruflin — Tue, 06 Nov 2007 17:03:22 GMT

I got it working now.

The following snippet is produced by the Java Alfresco Webservice API, omitting soapenv:actor and soapenv:mustUnderstand did also work for me (I need to get paging working using the php-sdk):


<ns1:QueryHeader
   xmlns:ns1="http://www.alfresco.org/ws/service/repository/1.0"
   soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next"
   soapenv:mustUnderstand="0">
   <ns2:fetchSize xmlns:ns2="http://www.alfresco.org/ws/headers/1.0">
      5
   </ns2:fetchSize>
</ns1:QueryHeader>
‍‍‍‍‍‍‍‍‍‍

Put the QueryHeader element directly into the soap header. Note the two different namespaces for QueryHeader and fetchSize.

Re: Repository Service: Batching of results

marian — Thu, 08 Nov 2007 15:15:45 GMT

I got it working now.

So did I thanks to your sample header.

So to answer my further questions:

The query() returns a result where the TotalRows member is set to the
size of the batch or less. It does NOT contain information on how many
rows to expect, only how many are in the current response.

The QuerySession-Member will be set only if there are more rows to be
fetched by a call to fetchMore().

The same is true of fetchMore(): The QuerySession it returns is valid for
the next call to fetchMore() or empty, indicating that all results have been
fetched.

This is all strictly by observation, not based on deeper digging in the code.
I would still appreciate a pointer to some documentation to substanciate
these observations.

But other than that it works for me fine now.

Thank you.

Ciao, MM