cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <>
Subject Re: Why Cocoon Stops processing all Requests URI the moment one of them has an exception
Date Fri, 02 Jul 2004 10:48:17 GMT
First, please avoid cross-posting.

On 02.07.2004 11:16, Arnab Sengupta wrote:

> I have a Cocoon pipeline that takes a huge xml as input. The stucture of 
> xml is:
> <Root>
> <Message>
> <!--- Other elements inside it -->
> </Message>
> <Message>
> <!--- Other elements inside it -->
> </Message>
> <Message>
> <!--- Other elements inside it -->
> </Message>
> </Root>
> Now I have an xsltc transformer taking an xsl, internally calls same 
> cocoon URI, based on occurance of "<Message>" tag.

To be correct: this does not happen by XSLTC, but afterwards by the 
CInclude transformer.

> <xsl:foreach select="Message>
>             <xsl:variable name="messageURL">
> cocoon://labData?messageNo=<xsl:value-of select="position()"/>
> </xsl:variable>
>             <cinclude:include ignoreErrors="true" src="{$messageURL}" />
> </xsl:foreach>
> Now when any one of these URI's fired through CInclude gets an exception, 
> other URI's are never processed at all. I mean i am not very sure whether 
> other URI's gets fired or they are aborted. Can someone please tell me 
> what will happen, if URI fired by the occurance of 2nd <Message> gets an 
> exception. Will the URI for 3rd Message be fired at all? Or if fired it 
> will be aborted in middle..?
> Also can anyone tell me whether CInclude waits for response of the URL 
> fired by it to return an xml ?

AFAIK CInclude requests are not processed in parallel and an exception 
bubbles up and stops the complete request.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message