Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 976E110D0C for ; Thu, 27 Jun 2013 08:02:49 +0000 (UTC) Received: (qmail 55999 invoked by uid 500); 27 Jun 2013 08:02:48 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 55692 invoked by uid 500); 27 Jun 2013 08:02:40 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 55659 invoked by uid 99); 27 Jun 2013 08:02:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jun 2013 08:02:32 +0000 X-ASF-Spam-Status: No, hits=2.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sprengerj22@gmail.com designates 209.85.215.53 as permitted sender) Received: from [209.85.215.53] (HELO mail-la0-f53.google.com) (209.85.215.53) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jun 2013 08:02:25 +0000 Received: by mail-la0-f53.google.com with SMTP id fs12so446842lab.40 for ; Thu, 27 Jun 2013 01:02:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=daEXuj/Y4oyZhYwBBT5MzjlUlk4gzji2sdpeIhHP+Z8=; b=iDgU31Iptx586FIE4TreuQczH+m2ajfJMOugf+sE+jVNKz+cx9Rz8m6efnIeqs2VZV OOqtA7ENVS09nPoCQwCwmVKLgQNIU/Lv3BhxucO5aMjxE0uKdKvXiBYwmu6fF0icMVSf eV2fPA31k+myninB1MZc8ISzmFOruNRFriooMw4sIjm9oXvR9Lsjw5X3T9E0xd7OtTfq QL9gvCM8MzyvvCdEXo4OehtsnSQW3vLmLoejzrhcSsyr0q8IAi77QbIYSp5w2Owze0W7 NV9HLHOZF7jp2yNPVDZVWEtRyMdq6fpZdZsMtZEaPz09rArzySYqM4ZYZ+T30gtaom4L v/CA== MIME-Version: 1.0 X-Received: by 10.112.29.17 with SMTP id f17mr3804672lbh.20.1372320125269; Thu, 27 Jun 2013 01:02:05 -0700 (PDT) Received: by 10.112.73.42 with HTTP; Thu, 27 Jun 2013 01:02:05 -0700 (PDT) In-Reply-To: References: <70BFF8B2-E852-4ACA-ADA6-E3AC5B033602@gmail.com> Date: Thu, 27 Jun 2013 10:02:05 +0200 Message-ID: Subject: Re: [CHAIN] Thoughts about o.a.c.chain2.Chain, o.a.c.chain2.Command and the base classes From: Jonas Sprenger To: Commons Developers List Content-Type: multipart/alternative; boundary=001a1133c69095bae404e01e2dc0 X-Virus-Checked: Checked by ClamAV on apache.org --001a1133c69095bae404e01e2dc0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Elijah, The =91Continue=92 and =91Completed=92 values look very similar to me, espe= cially in Unit tests. I suggest naming the two states: - Continue - Finished >With regards to an enum for status, wouldn't it be better to use a class s= o >that consumers could subclass it and add their own states if needed? As far as I know, there is not a decision about the third state 'Aborted' yet. So the question is, do the 3 states cover the complete set of possible values? Implementing the exception handling might show the need for more states. I would suggest sticking with the enum for now. The refactoring from an enum to a interface =91Processing=92 is not that big deal. regards, Jonas 2013/6/26 Elijah Zupancic > +1 to everything. > > With regards to an enum for status, wouldn't it be better to use a class = so > that consumers could subclass it and add their own states if needed? > > Thanks, > -Elijah > > > On Sat, Jun 22, 2013 at 4:30 AM, Benedikt Ritter >wrote: > > > > > Am 22.06.2013 um 12:57 schrieb Simone Tripodi >: > > > > > Hi Jonas, > > > > > >> > > >> I will provide a patch for > > >> CHAIN-98tomorow. The > > >> patch will only cover the refactoring of CONTINUE and > > >> COMPLETED processing results. > > >> > > > > > > nice to read that, looking forward to the patch! :) > > > > > >> But, I do not understand how exceptions should be handled in this > > context. > > >> A exception listener filters the exceptions and returns ABORTED if > > >> appropriate? > > > > > > let's postpone it and keep CONTINUE and COMPLETED only ATM - Benedikt > > > is working on an exception listener, let's see how it evolves and > > > let's evaluate later if/how ABORTED will be introduced. > > > > Yeah, well I'm not really working on it. But I'll do as soon as I got t= he > > time :) > > > > Benedikt > > > > > > > > Thanks in advance, all the best! > > > -Simo > > > > > > http://people.apache.org/~simonetripodi/ > > > http://twitter.com/simonetripodi > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > > > For additional commands, e-mail: dev-help@commons.apache.org > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > > For additional commands, e-mail: dev-help@commons.apache.org > > > > > > > -- > -Elijah > --001a1133c69095bae404e01e2dc0--