You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Mark Lundquist <ml...@comcast.net> on 2005/03/02 17:22:58 UTC
"Attempted to process incomplete pipeline" error?
Hi all,
Using 2.1.6...
I have something like:
<match pattern="**">
<generate src="cocoon:/content/{1} />
.
. (etc....)
.
<match pattern="content/**">
<select type="resource-exists">
.
. (blah blah blah)
.
<when test="something">
<redirect-to uri="somewhere" global="true">
The redirect is _external_ (not "cocoon:/somewhere).
Cocoon sends the redirect back to the user agent correctly... but every
time, I get a bunch of stackage in handled-errors.log, all about
"Attempted to process incomplete pipeline".
Question 1: How do I get rid of this error?
Question 2:...
For unrelated and uninteresting reasons, I will have to deploy the
production version of this site under Cocoon 2.1.5 (temporarily, and
will upgrade it to 2.1.6 soon). But in 2.1.5, I get an internal
redirect, even though the uri scheme isn't 'cocoon'! This looks like a
bug that must have been fixed in 2.1.6... does anyone know for sure?
(I checked the 'Changes' page on the Cocoon site, but didn't see
anything definitive...)
Thanks,
—ml—
Re: "Attempted to process incomplete pipeline" error?
Posted by Geert Josten <Ge...@daidalos.nl>.
> You're right in that there's no SAX events to serialize. However, I
> wonder if adding a serializer would quiet Cocoon's complaints of an
> incomplete pipeline? I believe that's what Lars was getting at.
No, the sitemap parser will complain that it is not legal to combine a redirect-to with a serialize
> Of course, the real solution to your problem is to do all your
> redirecting from flowscript. ;)
No need to use flowscript, could do a generate and serialize as well, though there is a difference:
a redirect-to is visible in the browser. Streaming with generate/serialize or flowscript not.
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: "Attempted to process incomplete pipeline" error?
Posted by Daniel McOrmond <dm...@gmail.com>.
You're right in that there's no SAX events to serialize. However, I
wonder if adding a serializer would quiet Cocoon's complaints of an
incomplete pipeline? I believe that's what Lars was getting at.
Of course, the real solution to your problem is to do all your
redirecting from flowscript. ;)
-Daniel
On Wed, 2 Mar 2005 10:33:07 -0800, Mark Lundquist <ml...@wrinkledog.com> wrote:
>
> On Mar 2, 2005, at 9:39 AM, Lars Huttar wrote:
>
> >> Question 1: How do I get rid of this error?
> >>
> > Did you try putting a <map:serialize /> after the redirect-to?
>
> hmm, well... I don't think that would be right! :-) There's no SAX
> stream to serialize.
>
> (And if there were one at this point in the pipeline execution — that
> is, if a generator had already been set — then it would be a mistake to
> try to redirect in the first place).
>
> But thx for the input :-)
> —ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: "Attempted to process incomplete pipeline" error?
Posted by Mark Lundquist <ml...@wrinkledog.com>.
On Mar 2, 2005, at 9:39 AM, Lars Huttar wrote:
>> Question 1: How do I get rid of this error?
>>
> Did you try putting a <map:serialize /> after the redirect-to?
hmm, well... I don't think that would be right! :-) There's no SAX
stream to serialize.
(And if there were one at this point in the pipeline execution — that
is, if a generator had already been set — then it would be a mistake to
try to redirect in the first place).
But thx for the input :-)
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: "Attempted to process incomplete pipeline" error?
Posted by Lars Huttar <la...@sil.org>.
Mark Lundquist wrote:
> Hi all,
>
> Using 2.1.6...
>
> I have something like:
>
> <match pattern="**">
> <generate src="cocoon:/content/{1} />
> .
> . (etc....)
> .
>
>
> <match pattern="content/**">
> <select type="resource-exists">
> .
> . (blah blah blah)
> .
> <when test="something">
> <redirect-to uri="somewhere" global="true">
>
> The redirect is _external_ (not "cocoon:/somewhere).
>
> Cocoon sends the redirect back to the user agent correctly... but
> every time, I get a bunch of stackage in handled-errors.log, all about
> "Attempted to process incomplete pipeline".
>
> Question 1: How do I get rid of this error?
>
Did you try putting a <map:serialize /> after the redirect-to?
Lars
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: "Attempted to process incomplete pipeline" error?
Posted by Daniel McOrmond <dm...@gmail.com>.
Mark,
I can help by answering question 2. There was indeed some 'bugage'
related to redirecting that was fixed in the 2.1.6 release.
<http://issues.apache.org/bugzilla/show_bug.cgi?id=26854>
-Daniel
On Wed, 2 Mar 2005 08:22:58 -0800, Mark Lundquist
<ml...@comcast.net> wrote:
> Question 2:...
>
> For unrelated and uninteresting reasons, I will have to deploy the
> production version of this site under Cocoon 2.1.5 (temporarily, and
> will upgrade it to 2.1.6 soon). But in 2.1.5, I get an internal
> redirect, even though the uri scheme isn't 'cocoon'! This looks like a
> bug that must have been fixed in 2.1.6... does anyone know for sure?
> (I checked the 'Changes' page on the Cocoon site, but didn't see
> anything definitive...)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org