Hi Jeroen, Great! This works like a charm for pipelines only involving a file generator.
There is a further problem, however, for pipelines in which both an eXist XQuery generator (pulling out an indexed XML resource from a database) and further XSL stylesheets need access to the request parameters. When the XQuery generator is called for in a <map:part>, it is impossible to pass the request parameters: <map:aggregate element="root"> <!-- get XML representation of request --> <map:part src="cocoon:/requestAsXML"/> <!-- get XQuery result --> <map:part src="cocoon:/{1}.xq"/> </map:aggregate> (with a separate match for the .xq part in the pipeline:) <map:match pattern="*.xq"> <map:generate src="xquery/simpleSearch.xq" type="xquery"> <map:parameter name="use-request-parameters" value="true"/> </map:generate> <map:serialize type="xml"/> </map:match> When this part is pulled into the aggregation, the request parameters can't be passed. ... I can probably bypass this aggregation step by mimicking it in my XQuery scripts (since the duplicate parameter names are passed and handled ok via use-request-parameters). But maybe there are better alternatives to this ad-hoc approach? Again, thanks very much for your kind and valuable advice! Ron Van den Branden --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]