Berin:
While your dealing with this stuff - could you take a look at the problem of the location value assigned to configuration elements that are created implicity. For example - if I have a configuration <configuration/> and I request the child configuration "fred" using config.getChild( "fred" ), I loose the location information when looking up location on the returned child configuration.
What would you like to see?
The whole problem with the dynamically generated items (i.e. configuration elements that did not originate from the file) is that they don't really map back to the original file.
We can set the location to something like this:
**DC, parent=${location}**
(DC = dynamically created).
Let me know what you want to see, and I can probably get it going.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
