Return-Path: Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list axis-user@xml.apache.org Received: (qmail 5499 invoked from network); 4 Dec 2001 19:23:28 -0000 Received: from c007-h012.c007.snv.cp.net (HELO c007.snv.cp.net) (209.228.33.219) by daedalus.apache.org with SMTP; 4 Dec 2001 19:23:28 -0000 Received: (cpmta 26418 invoked from network); 4 Dec 2001 11:23:19 -0800 Received: from 216.242.133.178 (HELO Mrichman) by smtp.telocity.com (209.228.33.219) with SMTP; 4 Dec 2001 11:23:19 -0800 X-Sent: 4 Dec 2001 19:23:19 GMT Message-ID: <006e01c17cf9$21703ff0$68fa0a0a@softmountain.com> Reply-To: "Mark A. Richman" From: "Mark A. Richman" To: References: Subject: Re: HTTP Authentication in Axis Date: Tue, 4 Dec 2001 14:23:18 -0500 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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Another good reason for getting away from the MessageContext method mangling: Implementing an interface seems impossible. Consider this: public interface IFoo { public int bar(Object baz) throws Exception; } implementing IFoo as a webservice becomes impossible: public class Foo implements IFoo { ... public int bar(Object baz) throws Exception { // No MessageContext param ... } } Is there some way to for Foo.bar() to delegate to a protected method that knows about MessageContext??? I don't think anyone wants to see an IFoo like this: public interface IFoo { public int bar(MessageContext mc, Object baz) throws Exception; } This becomes increasingly important if you convert your interface IFoo to WSDL. Thanks, Mark A. Richman http://www.markrichman.com ----- Original Message ----- From: "Wendell J Bouknight" To: Sent: Tuesday, December 04, 2001 10:49 AM Subject: Re: HTTP Authentication in Axis > That would be a good idea if the factory took the MessageContext or some > other parameter into consideration. The proposed solution I see so far > breaks when you have multiple incoming requests for different users. > >