commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dakota Jack <crackwil...@gmail.com>
Subject Re: [configuration] Any reason why JNDIConfiguration is readonly?
Date Wed, 27 Oct 2004 06:48:50 GMT
I really like the nutshell on Java's treatment of JNDI.  It is a great
job, I think.

Jack


On Wed, 27 Oct 2004 08:44:06 +0200, Eric Pugh <epugh@upstate.com> wrote:
> It should be..  However, I found it a real pain..   I think I need to really
> sit down and learn JNDI..  Write some unit tests of parsing the tree etc..
> I thought it would be a simple matter, ended up not being.  Not, I think,
> because of complexity, but just my own knowhow of JNDI.   Does anyone have a
> good reference to what the various things in JNDI are?  "Name" and
> "Contexts" etc...?   Most of the howto's I found seem too basic for me..
> 
> Eric
> 
> > -----Original Message-----
> > From: Oliver Heger [mailto:hegero@med.uni-marburg.de]
> > Sent: Wednesday, October 27, 2004 7:49 AM
> > To: Jakarta Commons Developers List
> > Subject: Re: [configuration] Any reason why JNDIConfiguration is
> > readonly?
> >
> >
> > Hmm, navigating through a tree based on a configuration key, creating
> > missing nodes if necessary and finally storing the value...
> >
> > Similar code is contained in HierarchicalConfiguration and I suppose in
> > XMLConfiguration, too, to update the internally used DOM tree. I wonder
> > if this could be generalized.
> >
> > Oliver
> >
> > Eric Pugh wrote:
> > > Well..  I started on the bind/rebind stuff.  and am having a really hard
> > > time of it...
> > >
> > > I can bind a property like this "newprop" just fine..  However,
> > a property
> > > like "my.newprop" fails..  I think I need to crawl the tree and find the
> > > correct context and then set that...  argh..
> > >
> > > I don't just want to save in a temporary storage because I want
> > to be able
> > > to persist via JNDI configuration changes.
> > >
> > > Eric
> > >
> > >
> > >>-----Original Message-----
> > >>From: Emmanuel Bourg [mailto:smanux@lfjr.net]
> > >>Sent: Monday, October 25, 2004 5:54 PM
> > >>To: Jakarta Commons Developers List
> > >>Subject: Re: [configuration] Any reason why JNDIConfiguration is
> > >>readonly?
> > >>
> > >>
> > >>Eric Pugh wrote:
> > >>
> > >>>Anyone have a good reason whe JNDIConfiguration doesn't support setting
> > >>>properties?  I was thinking of going for just a simple string
> > storing of
> > >>>properties, not binding in Datasources or anything funky like that...
> > >>>
> > >>>Eric
> > >>
> > >>How to you plan to implement this ? By playing with the
> > >>bind/rebind/unbind functions of the Context interface, or by storing the
> > >>new properties into a Map ?
> > >>
> > >>Emmanuel Bourg
> > >>
> > >>
> > >>---------------------------------------------------------------------
> > >>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > >>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message