Ole:
Je veux dire que je suis tout a fait d'accord avec toi concernant la question de l'internationalization des exceptions au niveau du serveur. Dans la plupart des systemes serveur et les infrastructures de logging, le message des exceptions arrive avec aucune consideration pour la langue natale des administrateurs. Bien sur, ici en France il y a beacoup de gens Francais qui ont une preference pour le travail dans leur langauge natale. Une observation: c'est peut-etre mieux de faire l'implantation d'internationalization du message directement dans les classes CascadingException and CascadingRuntimeException. De ce fait je suis en general d'accord avec votre proposition. +1 Cheers, Steve. > -----Original Message----- > From: Ole Bulbuk [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, 24 April, 2002 14:38 > To: 'Avalon Developers List' > Subject: AW: Do you *really* not need localized exceptions? > > > Hi Leo, Mike and all others, > > > The message in the exception does not always make sense to > > the user, and is often very unhelpful and cryptic. > > To me this doesn't seem to be the cure but the sickness. Since I can't > change this (and the lack of internationalization) for exception > from other > packages I can only do a better job with my own exceptions. > > > It may > > work some times, but then you have structured your entire > > Exception hierarchy around your own application, with the > > intent that they should be used to create messages on the > > client side. > > I always thought that the messages should be as human readable and > understandable as possible. Exception that are catched on the server side > are usually logged there and the administrator of the server application > (who usually doesn't understand much english) has to read them. > > > I prefer to keep Exceptions inside the application - when > > an error condition is presented to the user, I want to > > control how it is presented based on the current application > > context. > > Yes, nice. But how do you "control how it is presented based on > the current > application context" when you get something like a JDBCException. The text > is in a language you don't want to show and the exception type doesn't say > much. There has been a problem with the database but what: > 1. Is there a network problem, couldn't you connect? > 2. Is there a table or view missing? > 3. Did a constraint violation occur? > > In case #3 the user can usually do something about it. > In case #1 it might be worth for him to take a short look at the network > cable. > In case #2 only the database administrator can help and he should > be alarmed > (but how if you can't distinguish case #3 from the others?). > > What do you tell the user then? Do you simply say "There was some problem > with the database, please try again." until the user is totally frustrated > (because of case #1 or #2)? > > If somebody could show me a way to good error messages without localized > exceptions I would be very grateful (this would help me very much with all > the unlocalized exceptions I get everywhere). > This is the biggest problem I see at the moment in my Java software > development (if a customer would insist on meaningful error > messages in his > own language the company I work for might go bankrupt) so I would really > appreciate any and every help. > > With kind regards, > > 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
