Use exception's class name as a key?

1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User

Welcome to IWETHEY!

Post #144,979 by Arkadiy 3/9/04 8:36:55 AM Reply	Use exception's class name as a key? -- ...what happened to intelligence of this country? -- Sen. Kerry.
Post #144,984 by bluke 3/9/04 9:22:21 AM 3/9/04 9:31:14 AM Reply	That would lead to a lot of exception classes Basically what you are suggesting is that for every possible error create a new exception class. That is problematic for a number of reasons. 1. You then end up throwing a long list of exceptions making every one catch or throw the long list. The whole point of wrapping exceptions is so that the gui only ends up having to catch a small number of exceptions 2. You end up with a large number of exception classes Edited by bluke March 9, 2004, 09:31:14 AM EST Expand All History
Post #144,993 by tuberculosis 3/9/04 10:22:57 AM Reply	Create a wrapper exception class call it LocalizedException and provide messageKey and messageParams methods. Use the messageKey to lookup a format string in a resource bundle containing a message format string - then unify that with the messageParams with java.text.MessageFormat. You can have the exception class do the lookup of the bundle, or leave it to client code. I'd be inclined to put it in the exception itself - implementing something like toString(locale). The tree of research must from time to time be refreshed with the blood of bean counters. -- Alan Kay

I18N (internationalization) and exceptions - (bluke) - (3) - March 9, 2004, 08:14:49 AM EST

Use exception's class name as a key? -NT - (Arkadiy) - (2) - March 9, 2004, 08:36:55 AM EST

That would lead to a lot of exception classes - (bluke) - (1) - March 9, 2004, 09:31:14 AM EST

Create a wrapper exception class - (tuberculosis) - March 9, 2004, 10:22:57 AM EST

Like a flaming ant farm, only less organized.
34 ms