Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 12313 invoked from network); 2 Nov 2007 09:40:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Nov 2007 09:40:25 -0000 Received: (qmail 69826 invoked by uid 500); 2 Nov 2007 09:40:06 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 69771 invoked by uid 500); 2 Nov 2007 09:40:06 -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: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 69760 invoked by uid 99); 2 Nov 2007 09:40:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 02:40:06 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pzfreo@gmail.com designates 64.233.162.226 as permitted sender) Received: from [64.233.162.226] (HELO nz-out-0506.google.com) (64.233.162.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 09:40:06 +0000 Received: by nz-out-0506.google.com with SMTP id l1so576924nzf for ; Fri, 02 Nov 2007 02:39:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=NUHRIytEDq8KbVvYJ6+ErlI9b26cEbyK0o95PLAunGo=; b=daM0DG0HK7JT1r/B9YHbIGxzRnGQA6/YpOcSpZDkCPaYHqRlU/9apehfCxCU6ZHbPQUFlymRwcGKoMYCZuizGpIrPglB6x29FpvHnnZ/DSrgg+s5kMRP92NDgH1rqCJ1WMM4LCrsTPr8pZNBc/sEsbCULBK7dqvJQKLvBeSWSjc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=akwf5muiQo5QNH2Sa4nCZticRB/OauewDps/JLp3SSz/klibTUkkTRZ0ed5//TVOAZRfofOQX2u6FIcp2hqbCGrX81qrGord7K1hIb2P22EQ+JoxXDdHmhvbL+VdH0YF7oWnWBl6BCxPPvYM8XUzM7XaK0zkKwGVs8Tp1yTjA40= Received: by 10.142.80.7 with SMTP id d7mr403479wfb.1193996385169; Fri, 02 Nov 2007 02:39:45 -0700 (PDT) Received: by 10.142.97.12 with HTTP; Fri, 2 Nov 2007 02:39:45 -0700 (PDT) Message-ID: <88f5d710711020239i62388250w87fdf88cca3f8bb0@mail.gmail.com> Date: Fri, 2 Nov 2007 09:39:45 +0000 From: "Paul Fremantle" To: axis-dev@ws.apache.org Subject: Re: [Axis2] Role support for Axis2 handlers In-Reply-To: <9abd5e730711020225v2fd524ahf7cfccb2375b9000@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_14987_8734232.1193996385158" References: <9abd5e730711020225v2fd524ahf7cfccb2375b9000@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_14987_8734232.1193996385158 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline David I'd like to use this in Synapse too. Basically the issue is in mustUnderstand checking. I'd like to be able to specify one or more roles for a Synapse instance and then limit mustUnderstand checking to those roles. Paul On 11/2/07, David Illsley wrote: > > Hi all, > There's been at least one mention of role support on the user list > recently and it's piqued my interest. A quick scan of the code > suggests that there isn't anything in Axis2 to deal specifically with > role support and I'd quite like to add it. So, a couple of > questions... > > 1. Am I right in thinking there's no explicit role > support/configuration in Axis2? > 2. Does anyone onject to me adding some? > Specifically, some config xml+deployment code to add a RolePlayer > instance to the AxisConfiguration object which handlers can use if it > exists (and if they're interested) > > Cheers, > David > -- > David Illsley - IBM Web Services Development > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-dev-help@ws.apache.org > > -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org paul@wso2.com "Oxygenating the Web Service Platform", www.wso2.com ------=_Part_14987_8734232.1193996385158 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline David

I'd like to use this in Synapse too. Basically the issue is in mustUnderstand checking. I'd like to be able to specify one or more roles for a Synapse instance and then limit mustUnderstand checking to those roles.

Paul

On 11/2/07, David Illsley <davidillsley@gmail.com> wrote:
Hi all,
There's been at least one mention of role support on the user list
recently and it's piqued my interest. A quick scan of the code
suggests that there isn't anything in Axis2 to deal specifically with
role support and I'd quite like to add it. So, a couple of
questions...

1. Am I right in thinking there's no explicit role
support/configuration in Axis2?
2. Does anyone onject to me adding some?
    Specifically, some config xml+deployment code to add a RolePlayer
instance to the AxisConfiguration object which handlers can use if it
exists (and if they're interested)

Cheers,
David
--
David Illsley - IBM Web Services Development

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org




--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com ------=_Part_14987_8734232.1193996385158--