Ack! Fingers slipped! Here's what I meant to write:
> I did something like this once, to aggregate a list of html
> pages together. Each page had a [next] link at the bottom,
> and my pipeline basically followed these links. I think you
> want something similar. I don't have the code still, but
Alex Romayev wrote:
> I have a process in which in need to call the same
> pipeline recursively and aggregate the results.
>
> Basically, I have a pipeline which parses a paginated
> HTML page:
>
>
>src="http://www.foo.com?page={request-param:page}/>
>
>
>
>
> The pipeline needs to
Hi,
I have a process in which in need to call the same
pipeline recursively and aggregate the results.
Basically, I have a pipeline which parses a paginated
HTML page:
http://www.foo.com?page={request-param:page}/>
The pipeline needs to look for a particular record, if
it doesn't find
AFAIK it's not that easy. Maybe somebody else can correct me, but an
internal cocoon:/ request is handled the same way an external request is
handled. I.e. a pipeline is searched for it and if non is found (that's
the case for your failing action) an error is thrown. This is caught by
an error
Hi all,
I've been struggling with some error handling issues for several
days now. Perhaps the key to my problems can be found in the answer
to the question, can errors propagate beyond a pipeline call?
E.g. if I have the following pipeline:
It do
