Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 85026 invoked by uid 500); 29 Dec 2001 20:58:12 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Delivered-To: moderator for axis-dev@xml.apache.org Received: (qmail 70951 invoked from network); 29 Dec 2001 20:02:55 -0000 Message-ID: <000801c190a3$6e9aeb00$b42f893e@default> From: "Glyn Normington" To: Subject: Re: Using JNDI from Web Service Date: Sat, 29 Dec 2001 20:00:12 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C190A3.6D4B3980" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C190A3.6D4B3980 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Mark, You question was couched in general terms and, in general, the answer is = 'no' - you can't use JNDI from a web service implementation as the = implementation may not be in Java. ;-) For Java implementations, the answer is not always going to be 'yes', = firstly because JNDI may not be available on the platform and secondly = because the appropriate J2EE container type supporting the special = java:comp/env namespace may not be available. However, in the specific case of Axis, I'll have to pass as I'm not sure = whether the intention is to provide a J2EE container environment. = Perhaps someone else knows the intended direction of Axis in this = respect. Glyn Normington ------=_NextPart_000_0005_01C190A3.6D4B3980 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Mark,
 
You question was couched in general = terms and, in=20 general, the answer is 'no' - you can't use JNDI from a web service=20 implementation as the implementation may not be in Java. = ;-)
 
For Java implementations, the answer is = not always=20 going to be 'yes', firstly because JNDI may not be available on the = platform and secondly because the appropriate J2EE container type = supporting the=20 special java:comp/env namespace may not be available.
 
However, in the specific case of Axis, = I'll have to=20 pass as I'm not sure whether the intention is to provide a J2EE = container=20 environment. Perhaps someone else knows the intended direction of Axis = in this=20 respect.
 
Glyn = Normington
------=_NextPart_000_0005_01C190A3.6D4B3980--