Return-Path: Delivered-To: apmail-jakarta-hivemind-dev-archive@www.apache.org Received: (qmail 38460 invoked from network); 24 Apr 2006 21:32:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Apr 2006 21:32:19 -0000 Received: (qmail 81698 invoked by uid 500); 24 Apr 2006 21:32:19 -0000 Delivered-To: apmail-jakarta-hivemind-dev-archive@jakarta.apache.org Received: (qmail 81676 invoked by uid 500); 24 Apr 2006 21:32:18 -0000 Mailing-List: contact hivemind-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: hivemind-dev@jakarta.apache.org List-Id: Delivered-To: mailing list hivemind-dev@jakarta.apache.org Received: (qmail 81651 invoked by uid 99); 24 Apr 2006 21:32:18 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Apr 2006 14:32:18 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Apr 2006 14:32:17 -0700 Received: from brutus (localhost.localdomain [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0C37A7142B6 for ; Mon, 24 Apr 2006 21:31:09 +0000 (GMT) Message-ID: <15382591.1145914269047.JavaMail.jira@brutus> Date: Mon, 24 Apr 2006 21:31:09 +0000 (GMT+00:00) From: "Howard M. Lewis Ship (JIRA)" To: hivemind-dev@jakarta.apache.org Subject: [jira] Commented: (HIVEMIND-130) Chain of command "join points" In-Reply-To: <2041588511.1118582387560.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 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 [ http://issues.apache.org/jira/browse/HIVEMIND-130?page=comments#action_12376114 ] Howard M. Lewis Ship commented on HIVEMIND-130: ----------------------------------------------- Another option that occured to me would be to allow multiple elements when building a chain of command (using ChainFactory). Dependencies would be worked out inside each group independently, then the individually ordered lists would be concatinated to form the final result. You can kind of simulate this today by having one of the elements reference a chain-of-command service, but that's at lot of XML to type! Possibly, implementing and multiple s would be the most flexible solution. > Chain of command "join points" > ------------------------------ > > Key: HIVEMIND-130 > URL: http://issues.apache.org/jira/browse/HIVEMIND-130 > Project: HiveMind > Type: New Feature > Components: library > Versions: 1.1 > Reporter: Howard M. Lewis Ship > Priority: Minor > > The usefulnes of chain of command could be extended by adding "join points" to the command chain. I would define a join point as a no-op command that exists just for ordering other commands in the chian, i.e.: > > > > > > Of course, the joins themselves shoudl honor before and after attributes. The joins become a skeleton, that organize complex command chains into stages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org