From dev-return-8249-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Thu Oct 06 09:51:40 2005 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 58305 invoked from network); 6 Oct 2005 09:51:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Oct 2005 09:51:40 -0000 Received: (qmail 5002 invoked by uid 500); 6 Oct 2005 09:51:39 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 4803 invoked by uid 500); 6 Oct 2005 09:51:38 -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 4792 invoked by uid 99); 6 Oct 2005 09:51:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Oct 2005 02:51:38 -0700 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=HTML_30_40,HTML_MESSAGE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of trustin@gmail.com designates 64.233.184.197 as permitted sender) Received: from [64.233.184.197] (HELO wproxy.gmail.com) (64.233.184.197) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Oct 2005 02:51:41 -0700 Received: by wproxy.gmail.com with SMTP id i21so172023wra for ; Thu, 06 Oct 2005 02:51:16 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=hRU2K7HHHlVkiQtfIgTIcQAucAhVonH2VYvHrBCj5UW71jmBWj3JrA2bvKre5CGGyl5NRFJVzmS2OyuEGrYrwXYqYDDBRVyvGaPskmi8uAF8ThTP4K8yPNyIitwWkFirV0/j9+NisgdyEcMJR/m5ata1ielV00mNK0PkY+g68VU= Received: by 10.54.106.15 with SMTP id e15mr1041665wrc; Thu, 06 Oct 2005 02:51:16 -0700 (PDT) Received: by 10.54.71.11 with HTTP; Thu, 6 Oct 2005 02:51:16 -0700 (PDT) Message-ID: <768dcb2e0510060251r295fc96eh@mail.gmail.com> Date: Thu, 6 Oct 2005 18:51:16 +0900 From: Trustin Lee Reply-To: Trustin Lee To: Apache Directory Developers List Subject: Re: In process access to directory. In-Reply-To: <4332C82B.7090903@attachmate.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_22369_16504148.1128592276091" References: <768dcb2e05092119446f762e59@mail.gmail.com> <4332C82B.7090903@attachmate.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_22369_16504148.1128592276091 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I apologize for my late response first of all. 2005/9/23, Jacob S. Barrett : > > Trustin Lee wrote: > > 2005/9/21, Jacob Barrett > >: > > > > The source behind this (AbstractContextFactory) though expects one of > > the Configuration objects in the env, and from what I can tell there > > isn't one that just locates a directory by it's instance id. > > > > > > You can simply use StartupConfiguration because ApacheDS will ignore th= e > > request if the service is already started up. It will also return a > > JNDI context with an appropriate running user as you specified in your > > StartupConfiguration. > > Yeah, but since I want others that are not familiar to the ApacheDS to > be able to access the context that I have already setup for them in > process I was hoping for something a little more simple. > > I have started making a few alterations. I added an env value > "org.apache.ldap.server.jndi.service.instance" to specify the env you > want. If that value is not set and there is no cfg set then it will try > to load the "default" instance. This is a short term fix in my mind > though. When I get a bit more time I would like to use the provider URL > for this since that is more appropriate. Something along the lines of > / or :. Since technically a URL > must have a scheme followed by a colon the second option fits that > format, it is just odd to have arbitrarily named schemes. Regardless of > format the AbstractContextFactory would strip out the instance from the > URL and and pass the remainder of the URL up to the context like it does > now. Your idea on letting users provide instanceId in an url is great. I've file= d this issue to JIRA: http://issues.apache.org/jira/browse/DIREVE-270 Thanks, Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ ------=_Part_22369_16504148.1128592276091 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,

I apologize for my late response first of all.

2005/9/23, Jacob S. Barrett <jacobba@attachmate.com>:
Trustin Lee wrote:
> 2005/9/21, Jacob Barrett <JacobBa@attachmatewrq.com
> <mailto:= JacobBa@attachmatewrq.com&= gt;>:
>
>     The source behind this (AbstractCo= ntextFactory) though expects one of
>     the Con= figuration objects in the env, and from what I can tell there
> =     isn't one that just locates a directory by it's instance= id.
>
>
> You can simply use StartupConfiguration because Ap= acheDS will ignore the
> request if the service is already started up= .  It will also return a
> JNDI context with an appropriate= running user as you specified in your
> StartupConfiguration.

Yeah, but since I want others that ar= e not familiar to the ApacheDS to
be able to access the context that I h= ave already setup for them in
process I was hoping for something a littl= e more simple.

I have started making a few alterations.  I added an env = value
"org.apache.ldap.server.jndi.service.instance" to specif= y the env you
want.  If that value is not set and there is no = cfg set then it will try
to load the "default" instance.  This is a short te= rm fix in my mind
though.  When I get a bit more time I would = like to use the provider URL
for this since that is more appropriate.&nb= sp; Something along the lines of
<instance>/<basedn> or <instance>:<basedn>.&nbs= p; Since technically a URL
must have a scheme followed by a colon t= he second option fits that
format, it is just odd to have arbitrarily na= med schemes.  Regardless of
format the AbstractContextFactory would strip out the instance from the=
URL and and pass the remainder of the URL up to the context like it doe= s
now.

Your idea on letting users provide instanceI= d in an url is great.  I've filed this issue to JIRA:

http://= issues.apache.org/jira/browse/DIREVE-270

Thanks,
Trustin
<= /div>
--
what we call human nature is actually human habit
--
http://gleamynode.net/ ------=_Part_22369_16504148.1128592276091--