Some suggestions :

- keep the exceptions in the main package, we don't really need a sub package decicated to exceptions.

- add a default constructor to the exception.

- i would use a more generic ConfigurationException that may be subclassed later. I wouldn't rush on a specialized ConfigurationLoadException now.

- i'd like to see a ConfigurationException on the load() and save() methods of DOM4JConfiguration and PropertiesConfiguration before 1.0, otherwise the pending patch to handle the reloading will break the backward compatibility.

Emmanuel Bourg


Eric Pugh wrote:
Hi all,

I added a ConfigurationLoadException to
ConfigurationFactory.getConfiguration().  I think that is the only really
obvious place where it is needed.

If everybody is cool with this, I'd like to issue a last call for 1.0, and
start on the release path.  After the last call, let's hold off on any new
functional changes, focus on any bug fixing required, and get 1.0 out the
door!

Eric


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



Reply via email to