Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 10346 invoked from network); 18 May 2005 05:26:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 May 2005 05:26:07 -0000 Received: (qmail 56465 invoked by uid 500); 18 May 2005 03:27:30 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 56423 invoked by uid 500); 18 May 2005 03:27:29 -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 56392 invoked by uid 99); 18 May 2005 03:27:29 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=FORGED_RCVD_HELO,TO_ADDRESS_EQ_REAL X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from 226.70-84-120.reverse.theplanet.com (HELO glider.phpwebhosting.com) (70.84.120.226) by apache.org (qpsmtpd/0.28) with SMTP; Tue, 17 May 2005 20:27:27 -0700 Received: (qmail 29433 invoked from network); 18 May 2005 03:34:33 -0000 Received: from unknown (HELO ?192.168.8.19?) (219.137.210.158) by 226.70-84-120.reverse.theplanet.com with SMTP; 18 May 2005 03:34:33 -0000 Message-ID: <428AB57F.4060101@citycita.net> Date: Wed, 18 May 2005 11:24:47 +0800 From: Philippe Guillard User-Agent: Mozilla Thunderbird 0.8 (X11/20041020) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "users@cocoon.apache.org" Subject: Error handling for portal coplets ? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi all, Is it possible to use sitemap error handling in coplet contents ? How? I have a cachingURI coplet that gets information from another servlet. If this information is not available i want to give information to the user instead of the "The coplet XXXX is currently not available.". I handle error java.io.IOException exception in the sitemap like this OK : Then i put this in a cachingURI coplet, this is the temporaryUri pipeline : If the file is not found i don't get my error handled, but the usual message : The coplet external-1 is currently not available. Regards, Phil --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org