Return-Path: 
 <axis-dev-return-1501-apmail-xml-axis-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org
Received: (qmail 18995 invoked by uid 500); 1 Jun 2001 14:33:13 -0000
Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
list-help: <mailto:axis-dev-help@xml.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@xml.apache.org>
list-post: <mailto:axis-dev@xml.apache.org>
Delivered-To: mailing list axis-dev@xml.apache.org
Received: (qmail 18912 invoked from network); 1 Jun 2001 14:33:12 -0000
Received: from unknown (HELO platinum.allaire.com) (63.109.196.16)
  by h31.sny.collab.net with SMTP; 1 Jun 2001 14:33:12 -0000
Received: from c1vn (namaste.ne.mediaone.net [24.218.162.35]) by
 platinum.allaire.com with SMTP (Microsoft Exchange Internet Mail Service
 Version 5.5.2650.21)
	id KS34RCXL; Fri, 1 Jun 2001 10:33:31 -0400
Message-ID: <026b01c0eaa8$125d8ce0$1600a8c0@c1vn>
From: "Glen Daniels" <gdaniels@macromedia.com>
To: <axis-dev@xml.apache.org>
References: <OF667BAC33.899AB544-ON85256A5E.004E7D3B@raleigh.ibm.com >
Subject: Re: writing handlers
Date: Fri, 1 Jun 2001 10:35:14 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

> As for a use-case - write a header handler.  Would you rather
> write something like DebugHandler+DebugHeader or just a simple class
> with one method in it?  I know which one is easier to me.

Oh, I didn't actually notice this the first readthrough.

So, OK, I write:

class DebugHeaderHandler {
    public setDebugLevel(int level) { ...code... };
}

and then I deploy something like:

<headerHandler class="DebugHeaderHandler" qName="dbg:Debug"
               type="xsd:int" method="setDebugLevel"/>

Look about right?

OK, now you have the question of where you store whatever context data you got
from the header.  If it's a separate class like this, you need either a static
place to put context (like the Debug class), or you need some model of how you
share information between the header handler classes and a) other header
handlers, and b) service classes.  This can get complicated pretty fast, and it
allows a lot of non-standard models for information sharing, which might reduce
interoperability.

--Glen