Return-Path: 
 <commons-user-return-11911-apmail-jakarta-commons-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org
Received: (qmail 98916 invoked from network); 6 May 2005 17:00:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 6 May 2005 17:00:29 -0000
Received: (qmail 82438 invoked by uid 500); 6 May 2005 16:56:22 -0000
Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org
Received: (qmail 82370 invoked by uid 500); 6 May 2005 16:56:21 -0000
Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-user-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-user-help@jakarta.apache.org>
List-Post: <mailto:commons-user@jakarta.apache.org>
List-Id: "Jakarta Commons Users List" <commons-user.jakarta.apache.org>
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Delivered-To: mailing list commons-user@jakarta.apache.org
Received: (qmail 82257 invoked by uid 99); 6 May 2005 16:56:20 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=RCVD_BY_IP
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of samad.haytham@gmail.com
 designates 64.233.162.195 as permitted sender)
Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.195)
  by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 06 May 2005 09:56:20 -0700
Received: by zproxy.gmail.com with SMTP id 34so917115nzf
        for <commons-user@jakarta.apache.org>;
 Fri, 06 May 2005 09:53:28 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=aBIwmPUBsP3jq4529BnUtJ5PqPwKh+9O59Sv2/yocZkWX0aS3LQDnuaUL72Y07waoaKZzm/ORLszZySjKQ9mIxiGUdM2Y6AYnEpjJKZf9zf2gStMBzKkKBxhsw6/buOGE6zwgIN/sfGkxN9idVIMKG/HGMQuoW9dBqlTWbkdq1I=
Received: by 10.36.80.4 with SMTP id d4mr732332nzb;
        Fri, 06 May 2005 09:51:49 -0700 (PDT)
Received: by 10.36.10.4 with HTTP; Fri, 6 May 2005 09:51:18 -0700 (PDT)
Message-ID: <13c80f85050506095161f963e3@mail.gmail.com>
Date: Fri, 6 May 2005 11:51:18 -0500
From: Samad Haytham <samad.haytham@gmail.com>
Reply-To: Samad Haytham <samad.haytham@gmail.com>
To: commons-user@jakarta.apache.org
Subject: [chain] When does a filter run?
In-Reply-To: <42548DA4.5080006@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <42548DA4.5080006@gmail.com>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Question about how filters work as we are seeing behaviour that is a
little different from what we expected.  We setup a filter as the
second command in a 4 command chain.  Following is an example config
file.

<chain name=3D"myChain">
  <command id=3D"1"....
   />
  <command id=3D"myfilter"..... />
  <command id=3D"3".../>
  <command id=3D"4" ...../>
</chain>

If command 1 throws an Exception, myfilter's postprocess is never
called.  Looking at the code, we realized that the filters are
executed in reverse order from where an exception is thrown (or the
chain ends).  Meaning that the filter's postprocess method is only
called if the execute method is called.  What we wanted was a way to
have one filter's postprocess method handle any exceptions that are
thrown.  To enable that with how Chains currently works, we move our
filter to the beginning of the chain.  Are there any other ways to do
this?  Define a Filter (no matter where in the Chain - in our case it
was the last command called JobEnd) and guarantee that its postprocess
is called?

BTW, its been nice working with chains.  Any information as to what we
can expect in the next release?

Thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org