> To be fair, most commercial database vendors *do* have localized > exceptions--and this is something we can have the option to support > in the excalibur.i18n package if we want.
Of course JDBCException was an extreme example. But IOException would be another one. (Don't I have the permission? Did I misspell a directory? ...) There are subclasses of IOException but there are still many different texts found in a real IOException. And even if I know that it is a FileNotFoundException it is difficult to translate since the most important information is of course the name of the file and this usually isn't known further up the "calling hierarchy". > Not everyone is going to support internationalized exceptions, > but if we can provide the tools to make it easy, then there is > just that many more users of the Avalon code. As I said, I would be willing to provide the code. Cheers, Ole -- Ole Bulbuk Tel.: 0331/74759/60 Ernst Basler + Partner Fax: 0331/74759/90 Tuchmacherstr. 47 E-Mail: mailto:[EMAIL PROTECTED] 14482 Potsdam WWW: http://www.ebp.de -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
