geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manu George" <manu.t.geo...@gmail.com>
Subject Re: Implementing Global JNDI
Date Thu, 27 Apr 2006 06:14:07 GMT
I agree with what Dain said.  I also believe that as the spec says the J2EE
component enviroment should not be writable and we need not provide any
option for that either. It is not necessary. Apps can bind to other
namespaces.

On 4/26/06, Dain Sundstrom <dain@iq80.com> wrote:
>
> Are you planning on making the J2EE component enviroment (java:comp/
> env) writable?  I can see making the global tree writable, but am
> concerned about making the component environment itself writable.
> The J2EE 1.4 spec page 64 states:
>
> The container must ensure that the application component instances
> have only
> read access to their environment variables. The container must throw the
> javax.naming.OperationNotSupportedException from all the methods of the
> javax.naming.Context interface that modify the environment naming
> context
> and its subcontexts
>
> I suppose we could add an optional flag for non-compliant
> applications to allow them to modify their environment, but I think
> the default for the component environment should be read-only.
>
> BTW, I am in favor of making everything else writable.
>
> -dain
>
> On Apr 26, 2006, at 6:32 AM, Manu George wrote:
>
> > 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:
> > >
> > >
> > >>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* <david_jencks@yahoo.com
> > >>><mailto: david_jencks@yahoo.com>> 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 in
> > >>>    > the current application local JNDI Context. What is the
> > >>>    > HandleDelegate entry for?
> > >>>    >
> > >>>    > Thanks
> > >>>    > Manu
> > >>>
> > >>>
> > >>>
> > >>>
> > >
> > >
> > >
> > >
> >
>
>

Mime
View raw message