Return-Path: 
 <axis-dev-return-47017-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 33304 invoked from network); 11 Jul 2006 16:25:57 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 11 Jul 2006 16:25:57 -0000
Received: (qmail 41174 invoked by uid 500); 11 Jul 2006 16:25:53 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 41132 invoked by uid 500); 11 Jul 2006 16:25:53 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-dev@ws.apache.org>
List-Id: <axis-dev.ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 41121 invoked by uid 99); 11 Jul 2006 16:25:53 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 09:25:53 -0700
X-ASF-Spam-Status: No, hits=0.3 required=10.0
	tests=HTML_FONT_BIG,HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of mingcheu@us.ibm.com designates
 32.97.110.154 as permitted sender)
Received: from [32.97.110.154] (HELO e36.co.us.ibm.com) (32.97.110.154)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Jul 2006 09:25:52 -0700
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
 [9.17.195.106])
	by e36.co.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k6BGPVVb011356
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <axis-dev@ws.apache.org>; Tue, 11 Jul 2006 12:25:31 -0400
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com
 [9.17.195.169])
	by d03relay04.boulder.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id
 k6BGPUgn185104
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <axis-dev@ws.apache.org>; Tue, 11 Jul 2006 10:25:30 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
 k6BGPUrh020897
	for <axis-dev@ws.apache.org>; Tue, 11 Jul 2006 10:25:30 -0600
Received: from d03nm120.boulder.ibm.com (d03nm120.boulder.ibm.com
 [9.17.195.146])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
 k6BGPU02020893
	for <axis-dev@ws.apache.org>; Tue, 11 Jul 2006 10:25:30 -0600
To: axis-dev@ws.apache.org
Subject: Is there any J2EE security support in AXIS2?
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 HF144 February 01, 2006
Message-ID: 
 <OFA3FE1917.9A6DAFCF-ON872571A8.005A1A71-862571A8.0059AF7B@us.ibm.com>
From: Ming Cheung <mingcheu@us.ibm.com>
Date: Tue, 11 Jul 2006 11:30:15 -0500
X-MIMETrack: Serialize by Router on D03NM120/03/M/IBM(Release 7.0.1HF123 |
 April 14, 2006) at
 07/11/2006 10:25:29,
	Serialize complete at 07/11/2006 10:25:29
Content-Type: multipart/alternative;
 boundary="=_alternative 0059AF7A862571A8_="
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

--=_alternative 0059AF7A862571A8_=
Content-Type: text/plain; charset="US-ASCII"

I am planning to use AXIS2 within J2EE Security environment. Does AXIS2 
currently support J2EE security (with Security Manager enabled)? If yes, 
Could anyone please provide me some detail information of how to 
make/enable AXIS2 to work within J2EE Security environment?

One of examples of using J2EE security is using the doPrivileged 
constructs within a certain call path for accessing the protected 
resources. 
http://java.sun.com/j2se/1.3/docs/guide/security/spec/security-spec.doc4.html#20389

BTW, Does AXIS also support J2EE Security? 

Thank you,
Ming Cheung
--=_alternative 0059AF7A862571A8_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=4 face="Times New Roman">I am planning to use AXIS2 within
J2EE Security environment. Does AXIS2 currently support J2EE security (with
Security Manager enabled)? If yes, Could anyone please provide me some
detail information of how to make/enable AXIS2 to work within J2EE Security
environment?</font><font size=3><br>
</font><font size=4 face="Times New Roman"><br>
One of examples of using J2EE security is using the doPrivileged constructs
within a certain call path for accessing the protected resources. </font><font size=4 color=blue face="Times New Roman"><u><br>
</u></font><a href="http://java.sun.com/j2se/1.3/docs/guide/security/spec/security-spec.doc4.html#20389"><font size=4 color=blue face="Times New Roman"><u>http://java.sun.com/j2se/1.3/docs/guide/security/spec/security-spec.doc4.html#20389</u></font></a>
<br>
<br><font size=3>BTW, Does AXIS also support J2EE Security? <br>
<br>
Thank you,<br>
Ming Cheung</font>
--=_alternative 0059AF7A862571A8_=--