I try to get rid of naked RuntimeExceptions whenever I can. If a problem can be caused by user error or system config, it should throw a class of ours, and it should support I18N, as far as I've understood our conventions.
On Mon, Oct 6, 2008 at 6:24 PM, Christian Schneider <[EMAIL PROTECTED] > wrote: > Hi all, > > when there is a problem with the configuration i currently throw a simple > RuntimeException. I think this can be handled better. > I have found a class ConfigurationException but it only accepts a message > as i18 Message. Should this class be used? I do not like that much that it > always needs a resource definition. > Is internationalization for config errors that usefull? Whenever I got a > german exception I had much problems trying to google for it. So I > personally like english exceptions. > Another possibility would be to throw an AssertionError. As it is for > example an assertion that a certain property is not null. > > Any ideas? > > Greetings > > Christian > > -- > > Christian Schneider > --- > http://www.liquid-reality.de > >
