Eric,
I have been thinking about this problem for a while, but I really don't see a way to get ConfigurationXMLDocument running with a reasonable amount of work. So I would opt for removing this class in the 1.0 release and later add it again. I think, Emanuel is on the same opinion.
I have made a suggestion for a more hierarchical design of [configuration], which can be found here:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=52582
This approach would make integration of ConfigurationXMLDocument very easy.
Oliver
Eric Pugh wrote:
Oliver, do you know what changes need to be done to make ConfigurationXMLDocument work? Or do you think we should remove it for now, and get the 1.0 release out, so we can start on 2.0 refactoring?
Eric
-----Original Message----- From: Oliver Heger [mailto:[EMAIL PROTECTED] Sent: Thursday, July 29, 2004 7:53 AM To: Jakarta Commons Users List Subject: Re: [configuration] Can't get it to work properly
Hello Marty,
usage of ConfigurationXMLDocument is quite problematic ATM because there have been changes on other classes which brake this class. If you build [configuration] from the actual CVS sources, you will see that the unit tests for ConfigurationXMLDocument fail.
Currently there is no easy solution for this problem. AFAIK it is planed that ConfigurationXMLDocument won't be part of the 1.0 release of [configuration] (which will come very soon hopefully). After that some refactoring and redesign will be performed which solve the problems. (Can somebody else confirm this or correct me?)
What could help you with your actual problem is the following: If you have only one XML configuration file you have to process, you can load it directly using HierarchicalXMLConfiguration (and don't use ConfigurationFactory). If you then create a ConfigurationXMLDocument from this configuration, the resulting XML document will probably keep its structure and can be processed by Digester.
Oliver
[snip]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
