Jonas Lundberg wrote:
The xquery stores the XML file in eXist.
Thus, if I try to insert the xml file using an Xinclude in discuss.xq,
and then use an xinclude transformer after generation,
then it will be put there *after* the query is executed. Which is not
useful in this case, since the XML is needed during execution.
Hi,
I'm curious about this too. I've so far serialised the XML in
javascript, stored it in the session (this can be improved I think, it's
'not great') and passed the serialised version as a parameter to the
xquery. In the xquery you can use util:eval() to de-serialise the XML
(possibly skipping the XML declaration though). It's not great, but it
works. Serialising your XML isn't 'cool', but when you use XML-RPC (like
I do) it'll be serialised anyway, doesn't it?
Regards,
Huib.
Regards
Hans
On 1/5/06, Geert Josten <[EMAIL PROTECTED]> wrote:
Thanks for the replies.
The problem is that I then have use the xml in a pipeline that starts
with an xquery generator (this is the pipeline I call from the
flowscript):
<map:generate src="xq/discuss.xq" type="xquery">
<map:parameter name="cleanedxml" value="{flow-attribute:cleanxml}"/>
How is the xquery using the xml in the parameter? Is it an idea to have another
pipe that
*generates* the discuss.xq which has your cleanedxml fragment included
somewhere?
Cheers,
Geert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
