Berin Loritsch wrote:
Stephen McConnell wrote:
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.
A dynamic element should have the same location as the element it is created from.
Basically I have a test case that I want to turn into something useful. At the moment I'm getting this:
Cause: org.apache.avalon.framework.configuration.ConfigurationException
Message: No attribute named "fred" is associated with the configuration element "configuration" at [EMAIL PROTECTED]
I think the error message should be as is but ending with " at " ${location}. And that ${location} should be present for all elements including dynamically created elements.
Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
