Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 34814 invoked from network); 9 Nov 2004 06:55:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 9 Nov 2004 06:55:10 -0000 Received: (qmail 15056 invoked by uid 500); 9 Nov 2004 06:54:56 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 14968 invoked by uid 500); 9 Nov 2004 06:54:55 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 14950 invoked by uid 99); 9 Nov 2004 06:54:54 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of ajith.ranabahu@gmail.com designates 64.233.170.201 as permitted sender) Received: from [64.233.170.201] (HELO rproxy.gmail.com) (64.233.170.201) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 08 Nov 2004 22:54:52 -0800 Received: by rproxy.gmail.com with SMTP id y7so35920rne for ; Mon, 08 Nov 2004 22:54:50 -0800 (PST) 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:references; b=WkSW0q15O7/E2G37HrMUbSarwnJ3U+TMzoZNzd1VM7EDtN97uDafkjZMYZgZPYozZwX6DlUzLNeWimtzWJhm9AYCrPmo2rbxvA3ps/J4QAopWAVR3B/exFrRfiFOw8XMZVFZAcNre5C5+uJI9ElKRpNpgGrqN1DlyYl1m1SlI0w= Received: by 10.38.79.2 with SMTP id c2mr116603rnb; Mon, 08 Nov 2004 22:54:50 -0800 (PST) Received: by 10.38.209.26 with HTTP; Mon, 8 Nov 2004 22:54:50 -0800 (PST) Message-ID: Date: Tue, 9 Nov 2004 12:54:50 +0600 From: Ajith Ranabahu Reply-To: Ajith Ranabahu To: axis-dev@ws.apache.org, Srinath Perera Subject: Re: [Axis2] Phase Handlers In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <023601c4c573$1558f980$0965a8c0@deepal> <005101c4c5eb$65258280$0bffff0a@LANKABOOK> <033d01c4c60c$9a087810$0965a8c0@deepal> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N not much of thoughts but I have a single,very important question * who/what is going to determine the order of the handlers INSIDE the phase then. Lets say you want to run the logging handler (the most famous example) before all the handlers. In other words you want it to be the first handler of the first phase. How can this be done? On Tue, 9 Nov 2004 12:32:34 +0600, Srinath Perera wrote: > Sorry, bit late to catch up but seems (at least to me:D) we are > agreeing on something wrong!! > > > > In the case of before and after they refer to "handlers". The phases > > > > are NOT ordered dynamicaly, they are just static. (we can even give > > > > the phase order in the axis global config file if we want to). However > > > > every handler MUST belong to at least one phase. > > Here we going to decide on before, after refers to Handler names .. > not the phase name. To me that is wrong!!! > 1) The Handler writers do not know the handlers names of other > handlers (Handler names are subjected to change .. the rules based on > Handler names do not going to help us like set of defined phase.. so > all the rules should based on phases .. not handler names ) > 2) If before/after is a handlers we do not need phases at all, we can > get all the orders by just referring to handlers! > > To me the rationale for Phases to Exist is handler developers do not > know the names of Handlers .. so we have defined phases, encryption > Phase, authentication phase ...RM phase logging phase ;) > All the rules are based on phases not handlers so the handler > developers can say I need to run the RM after authentication but > before encryption etc ......with out knowing the finer details about > the Encryption or security handlers. > thoughts? > Thanks > Srinath > -- Ajith Ranabahu