I had a short glance at your code (not much time ATM). This seems to be
similar to my own ideas. Comments inline.
Emmanuel Bourg wrote:
[snip]
- a ConfigurationNode interface is introduced, it's an abstract node
with basic navigation methods like getElements(), createNode(),
getName(). Its
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
basic for me..
Eric
-Original Message-
From: Oliver Heger [mailto:[EMAIL PROTECTED]
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
Oliver Heger wrote:
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
: [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
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
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:[EMAIL PROTECTED]
Sent: Monday, October 25, 2004 5:54 PM
To: Jakarta Commons Developers List
Subject: Re: [configuration] Any reason
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..