Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <42261994.7050501@daidalos.nl>
Date: Wed, 02 Mar 2005 20:52:52 +0100
From: Geert Josten <Geert.Josten@daidalos.nl>
Organization: Daidalos BV
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: "Attempted to process incomplete pipeline" error?
References: <5701F19C-8B37-11D9-9A03-000A95D6B56C@comcast.net>
	 <4225FA3B.2000701@sil.org>
	 <85848F6E-8B49-11D9-9A03-000A95D6B56C@wrinkledog.com>
 <d3711066050302110664713d00@mail.gmail.com>
In-Reply-To: <d3711066050302110664713d00@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

> 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