Hi!

Just started working with the newest SOAP driver and query-ex, and did think
I had it working:

I have a policy that queries (query-ex) for user objects on the subscriber
channel:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.11.4904">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query-ex class-name="User" max-result-count="10" scope="subtree">
<search-class class-name="User"/>
<search-attr attr-name="CN">
<value type="string">u*</value>
</search-attr>
<read-attr/>
</query-ex>
</input>
</nds>

--
This is transformed into valid web service query in the output transform,
and transformed from web service query results to instance documents in the
input transform (last part shown only):

<attr attr-name="Misc14">
<value type="string">u32044</value>
</attr>
</instance>
<query-token>10</query-token>
<status event-id="0" level="success"/>
</output>
</nds>

The <query-token> element is added by the policy, based on the answer from
the web service (that tells there are more data to get). The value (10) is
also custom injected.

This instance document hits the policy that initiated the query, but instead
of asking for the next results, the engine automatically cancels the query-
ex:

[06/01/11 14:11:57.677]:CMG PT: Query from policy
[06/01/11 14:11:57.677]:CMG PT:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.11.4904">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query-ex cancel="true">
<query-token>10</query-token>
</query-ex>
</input>
</nds>

I would expect this instead:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.11.4904">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<query-ex>
<query-token>10</query-token>
</query-ex>
</input>
</nds>

Why does the engine automatically inject cancel=true?
Is the token not valid? (does the engine have to create the token value?)
Anyone?

Regards,
Toralf Lote