Return-Path: Mailing-List: contact soap-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list soap-dev@xml.apache.org Received: (qmail 44216 invoked from network); 28 Dec 2001 11:40:31 -0000 Received: from snowstorm.mail.pipex.net (158.43.192.97) by daedalus.apache.org with SMTP; 28 Dec 2001 11:40:31 -0000 Received: (qmail 2768 invoked from network); 28 Dec 2001 11:40:29 -0000 Received: from userc030.dsl.pipex.com (HELO higrade) (62.188.50.30) by smtp-6.dial.pipex.com with SMTP; 28 Dec 2001 11:40:29 -0000 Reply-To: From: "davout" To: Subject: RE: Access to Soap message header data? Date: Fri, 28 Dec 2001 11:41:17 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Axis is still in alpha. I'm reluctant to use anything that is pre-release. When is Axis due for formal release? -----Original Message----- From: Sam Ruby [mailto:rubys@us.ibm.com] Sent: 28 December 2001 11:26 To: soap-dev@xml.apache.org Subject: RE: Access to Soap message header data? "davout" wrote: > > It's a RPC Java class. > > If I can't get access to the header info how am I supposed to authenticate > that the service consumer can access this service? The stock quote sample in Axis is an example of an RPC class with a simple authentication handler based on SOAP headers. http://xml.apache.org/axis/ - Sam Ruby