Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 49140 invoked from network); 9 Mar 2006 17:53:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Mar 2006 17:53:15 -0000 Received: (qmail 47619 invoked by uid 500); 9 Mar 2006 17:53:08 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 47531 invoked by uid 500); 9 Mar 2006 17:53:08 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 47488 invoked by uid 99); 9 Mar 2006 17:53:07 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Mar 2006 09:53:07 -0800 X-ASF-Spam-Status: No, hits=2.3 required=10.0 tests=DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [63.240.77.81] (HELO sccrmhc11.comcast.net) (63.240.77.81) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Mar 2006 09:53:07 -0800 Received: from [127.0.0.1] (waltham-nat.ma.lycos.com[209.202.205.1]) by comcast.net (sccrmhc11) with ESMTP id <2006030917524501100887h4e>; Thu, 9 Mar 2006 17:52:45 +0000 Message-ID: <44106B6C.2030704@comcast.net> Date: Thu, 09 Mar 2006 12:52:44 -0500 From: Justin Hannus User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: users@cocoon.apache.org Subject: handling errors in parts Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I can't seem to get an aggregate pipeline part to respect or handle errors correctly when an exception occurs in one of the aggregate parts. It almost seems as if its impossible. This is whats happening... When an exception occurs in the a pipeline which is called as one of the part elements, the erroring pipeline or parent pipelines do not handle the errors correctly. In fact, the is completely ignored. What happens is the sitemap processing continues even after the exception occurs and, eventually the main entry matching pipeline's is invoked. This is bad because when using a cocoon:// request as your src any pipelines under that cocoon:// request will continue processing as if no error has occurred but..... you will still see the cocoon error page as if processing actually stopped! I have a pipeline which aggregates several other pipelines and then writes the generated content to disk. If there is an exception in one of the aggregate parts I need the sitemap processing to stop and handle the exception appropriately. Instead the generated content, which has errored and therefore invalid, is still written to disk. If I remove the aggregate pipeline and just use a regular generator the handle-errors is respected correctly and processing stops before writing the content. Am I misusing the elements? Or is this the expected behavoir? Thanks so much, -- Justin Hannus Software Engineer | Infrastructure | Lycos Inc. justin.hannus@lycos-inc.com [781] 370-2988 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org