On Dec 9, 2004, at 12:32 AM, Mark Womack wrote:
My recent commits don't have anything to do with this issue. They certainly don't extend the Configurator api to include a getErrorList method or a doConfigure method that takes a list to put errors into.
Sorry, I saw the new definitions of doConfigure(InputStream) and jumped to the wrong conclusions.
It looks like you were adding doConfigure(InputStream) methods to something configurator related. Would you consider making it
doConfigure(InputStream stream, String baseURI);
where baseURI may be null and is ignored for non-XML configurators. An XML document contains relative URI's can't be resolved without a baseURI (source of the recent thread on involving log4j.dtd).
Just from this description, it appears that only JoranConfigurator has this "stateful" feature. Maybe a better way to handle this would be through a callback mechanism. Then the client could do whatever it pleases. Store it in a list for later use, whatever.
If this is a feature one would want for all Configurators, the interface would need to be updated to include the method to register the callback.
Since I don't think any of the configurators are asynchronous, it just seems simpler to pass a List than to register callbacks (which would again make the configurator stateful).
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
