Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 57715 invoked from network); 25 Sep 2007 19:36:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Sep 2007 19:36:19 -0000 Received: (qmail 68535 invoked by uid 500); 25 Sep 2007 19:36:09 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 68317 invoked by uid 500); 25 Sep 2007 19:36:08 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 68306 invoked by uid 99); 25 Sep 2007 19:36:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2007 12:36:08 -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 akarasulu@gmail.com designates 64.233.162.227 as permitted sender) Received: from [64.233.162.227] (HELO nz-out-0506.google.com) (64.233.162.227) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Sep 2007 19:36:09 +0000 Received: by nz-out-0506.google.com with SMTP id o1so1142067nzf for ; Tue, 25 Sep 2007 12:35:48 -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:sender:to:subject:mime-version:content-type:x-google-sender-auth; bh=2W8juhbctwH8CY6mUAGXzD6Hd7ODWmmmUCBcIdYEujA=; b=SnwZU2eXwmtYlZ8mudYDVqNLyL3//WvyaS1R302OZe3g4JK9k8GQGQNX/mTwZkYVvrL1wgeBbORc/fpfzRshtgPgpJOk5Cu5Nyv9GKjc0ptDv0hac2mT8B/MO+sjUD/LG+Fj6nYjp+KwKkfyiS2IY/fwMtyBqCSIPd/dVcEGI64= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=altRPaqwzefHVqXrKFgK+orr1+IYEq/EaN8Nq+EH0v0c1r/hka5vNkrRcfcjHPWYURLZ5NJUeb9FTdUwHFB1plqS0+6CQo0zsuccn2xOlPPWflI0sfQln4LGI2zsDQv01NXqNdCwEfBNrMUIgB8BuC8BTvFUSGa+Si06SYIGD2Q= Received: by 10.115.32.1 with SMTP id k1mr1596678waj.1190748947598; Tue, 25 Sep 2007 12:35:47 -0700 (PDT) Received: by 10.115.76.8 with HTTP; Tue, 25 Sep 2007 12:35:47 -0700 (PDT) Message-ID: Date: Tue, 25 Sep 2007 15:35:47 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: [JNDI] Abstracting away JNDI providers MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2886_30766464.1190748947600" X-Google-Sender-Auth: 48c8011a2f139bce X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_2886_30766464.1190748947600 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi studio team, I was wondering if you guys have a means to abstract the JNDI context factory used in connections depending on the JVM being used. I have a similar need to get the JNDI context factory name based on the JVM that the server is running on so I thought I might ask if you already have something in place. As you know the over the wire JNDI provider's InitialContextFactory class is JVM specific. Did you guys encapsulate this so studio uses the proper one when running on different JVMs? Thanks, Alex ------=_Part_2886_30766464.1190748947600 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi studio team,

I was wondering if you guys have a means to abstract the JNDI context factory used in
connections depending on the JVM being used.  I have a similar need to get the JNDI
context factory name based on the JVM that the server is running on so I thought I might
ask if you already have something in place.

As you know the over the wire JNDI provider's InitialContextFactory class is JVM specific. 
Did you guys encapsulate this so studio uses the proper one when running on different JVMs?

Thanks,
Alex
------=_Part_2886_30766464.1190748947600--