Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 32488 invoked from network); 26 Apr 2006 13:33:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Apr 2006 13:33:07 -0000 Received: (qmail 75972 invoked by uid 500); 26 Apr 2006 13:33:03 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 75933 invoked by uid 500); 26 Apr 2006 13:33:02 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 75922 invoked by uid 99); 26 Apr 2006 13:33:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Apr 2006 06:33:02 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of manu.t.george@gmail.com designates 64.233.162.205 as permitted sender) Received: from [64.233.162.205] (HELO nz-out-0102.google.com) (64.233.162.205) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Apr 2006 06:33:01 -0700 Received: by nz-out-0102.google.com with SMTP id 4so1301495nzn for ; Wed, 26 Apr 2006 06:32:39 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=jv67pSqRE8dyDLQ0EiyeOSQGt0ZdOJy3GAjtw5ku0au8SbHd5c3wv1OC3CHcS8FNK/1znSz5SGG8GZBmrw/oaK6A4fZ0huzZ9tWU/8IDhRRhGZivXXHCudhmtu+RjLJUESqfb65Q0QMdaYjnGyxbkW38vSWq7FWUoJv2GuL0wlc= Received: by 10.65.100.12 with SMTP id c12mr656619qbm; Wed, 26 Apr 2006 06:32:39 -0700 (PDT) Received: by 10.64.148.8 with HTTP; Wed, 26 Apr 2006 06:32:09 -0700 (PDT) Message-ID: <466797bd0604260632r147bd3c3u898774514f07e324@mail.gmail.com> Date: Wed, 26 Apr 2006 19:02:09 +0530 From: "Manu George" To: dev@geronimo.apache.org Subject: Re: Implementing Global JNDI In-Reply-To: <444F6BD7.1030202@worldonline.fr> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4187_22816410.1146058329197" References: <2ed2f49c0604210240i6aeb689dnf5baf7e5f0cd7bd0@mail.gmail.com> <466797bd0604250734l7a09562eg34be2e8d1826bd8a@mail.gmail.com> <466797bd0604260015p7368f630h9414a9cafa0c6be3@mail.gmail.com> <444F24D8.7070804@worldonline.fr> <2ed2f49c0604260501sc22dfcbg4ace0ca0894efd54@mail.gmail.com> <444F6BD7.1030202@worldonline.fr> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_4187_22816410.1146058329197 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, Guillaume I guess if a writable context is implemented still the approach given above should work. As we will be using the ENCConfigBuilder only to populate the ENC during startup the interfaces can be used to refer to the gbeans representing the deployed artefacts. Whatever we will be writing t= o context from apps would be done after startup of server and lost at shutdown. So there would not be any problem due to geronimo using interfaces to get the GBean names as what we will be adding at runtime will not be gbeans and we will not use ENCConfigBuilder. Am I right? Now a new property for jndiname will also be required in the plans for the connectors. P.S.This property was actually present in the older versions of geronimo bu= t was removed. I also remember david jencks mentioning in the mailing list that he had a working implementation of a context which he removed for some reason. Thanks Manu > > > >On 4/26/06, Guillaume Nodet wrote: > > > > > >>When a JNDI context is created for a given configuration, the interface > >>name is used to determine the name of the gbean that will be mapped to > >>this JNDI reference (and to create a proxy ?). > >>Take a look at o.a.g.naming.ENCConfigBuilder#addResourceRefs. > >>But I guess this is irrelevant if the objects are bound when they are > >>created. > >> > >>Btw, should the global JNDI tree be read-only, or read-write ? > >>IMHO, a read-write global JNDI tree would be very usefull. > >> > >>Cheers, > >>Guillaume Nodet > >> > >> > >>Manu George wrote: > >> > >> > >> > >>>Thanks David. > >>> > >>>Guillaume , Which proxy in the JNDI Tree are you referring where > >>>geronimo requires the main interface name? Are you speaking of > >>>UserTransaction etc? I thought those were standard names that we can > >>>use to access them and will not be provided in DD? Please clarify and > >>>correct me if I am wrong. > >>> > >>>Thanks > >>>Manu > >>> > >>>On 4/25/06, *David Jencks* >>>> wrote: > >>> > >>> It's required for corba ejb references. > >>> > >>> david jencks > >>> > >>> On Apr 25, 2006, at 7:34 AM, Manu George wrote: > >>> > >>> > Hi, > >>> > I have a question regarding one of the objects present i= n > >>> > the current application local JNDI Context. What is the > >>> > HandleDelegate entry for? > >>> > > >>> > Thanks > >>> > Manu > >>> > >>> > >>> > >>> > > > > > > > > > ------=_Part_4187_22816410.1146058329197 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, Guillaume
   I guess if a writable context is implemented still the approach given above should work.   As we will be using the ENCConfigBuilder only to populate the ENC during startup the interfaces can be used to refer to the gbeans representing the deployed artefacts.   Whatever we will be writing to context from apps would be done after startup of server and lost at shutdown.  So there would not be any problem due to geronimo using interfaces to get the GBean names as what we will be adding at runtime will not be gbeans and we will not use ENCConfigBuilder.  Am I right?

Now a new property for jndiname will also be required in the plans for the = connectors.
 
P.S.This property was actually present in the older versions of geronimo but was removed. I also remember david jencks mentioning in the mailing list that he had a working implementation of a context which he removed for some reason.

Thanks
Manu


>
>On 4/26/06, Guillaume Nodet <= guillaume.nodet@worldonline.fr> wrote:
>
>
>>Wh= en a JNDI context is created for a given configuration, the interface
&g= t;>name is used to determine the name of the gbean that will be mapped t= o
>>this JNDI reference (and to create a proxy ?).
>>Take = a look at o.a.g.naming.ENCConfigBuilder#addResourceRefs.
>>But I g= uess this is irrelevant if the objects are bound when they are
>>c= reated.
>>
>>Btw, should the global JNDI tree be read-only, or r= ead-write ?
>>IMHO, a read-write global JNDI tree would be very us= efull.
>>
>>Cheers,
>>Guillaume Nodet
>>= ;
>>
>>Manu George wrote:
>>
>>
>&= gt;
>>>Thanks David.
>>>
>>>Guillaume ,= Which proxy in the JNDI Tree are you referring where
>>>geroni= mo requires the main interface name?  Are you speaking of
>>>UserTransaction etc? I thought those were standard names th= at we can
>>>use to access them and will not be provided in DD?= Please clarify and
>>>correct me if I am wrong.
>>>= ;
>>>Thanks
>>>Manu
>>>
>>>O= n 4/25/06, *David Jencks* <dav= id_jencks@yahoo.com
>>><mailto: david_jencks@yahoo.com>> wrote:
>>>
>>>&n= bsp;   It's required for corba ejb references.
>>&g= t;
>>>    david jencks
>>>
&= gt;>>    On Apr 25, 2006, at 7:34 AM, Manu George= wrote:
>>>
>>>    > Hi,
>>= ;>    >       =   I have a question regarding one of the objects present in
>>>&n= bsp;   > the current application local JNDI Context. What= is the
>>>    > HandleDelegate entry fo= r?
>>>    >
>>>  &= nbsp; > Thanks
>>>    > Manu
>>>
>&g= t;>
>>>
>>>
>
>
>
>
<= /blockquote>

------=_Part_4187_22816410.1146058329197--