Return-Path: 
 <geronimo-dev-return-2384-apmail-incubator-geronimo-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org
Received: (qmail 81282 invoked by uid 500); 25 Aug 2003 22:15:43 -0000
Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:geronimo-dev-help@incubator.apache.org>
list-unsubscribe: <mailto:geronimo-dev-unsubscribe@incubator.apache.org>
list-post: <mailto:geronimo-dev@incubator.apache.org>
Reply-To: geronimo-dev@incubator.apache.org
Delivered-To: mailing list geronimo-dev@incubator.apache.org
Received: (qmail 81241 invoked from network); 25 Aug 2003 22:15:42 -0000
Received: from msexchange00.multex.com (204.255.41.71)
  by daedalus.apache.org with SMTP; 25 Aug 2003 22:15:42 -0000
Received: by msexchange00 with Internet Mail Service (5.5.2653.19)
	id <Q06HX4LZ>; Mon, 25 Aug 2003 17:28:51 -0400
Message-ID: <79B184B0417FD41184DB00508BA540B8058C31A0@corpmail01>
From: "Cabrera, Alan" <Alan.Cabrera@reuters.com>
To: "'geronimo-dev@incubator.apache.org'"
	 <geronimo-dev@incubator.apache.org>
Subject: RE: [i18n] Hardcoded message strings
Date: Mon, 25 Aug 2003 17:28:51 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


> -----Original Message-----
> From: Dain Sundstrom [mailto:dain@coredevelopers.net] 
> 
> On Monday, August 25, 2003, at 09:58 AM, Alex Blewitt wrote:
> 
> > On Monday, Aug 25, 2003, at 15:25 Europe/London, gianny 
> DAMOUR wrote:
> >
> > authFailed=User %{0} cannot log in

> 
> I think that the type of messages you have above are a very 
> small class 
> of user exceptions as opposed to system exceptions.  Most exceptions 
> are things generaic things like IllegalArgument, like IO failed, or 
> transaction would not commit for some strange reason.  These normal 
> type of exception are not user display able, as a normal user would 
> have no idea what it means and your normal sys admin can't do 
> anything 
> about.  On the other hand there are a certain class of 
> exceptions which 
> are user display able and you have some good examples above.  
> If we are 
> going to take the i18 path, I think we should first divide exceptions 
> into internal system exceptions and user displayable exceptions.

You have touched on a point that I brought up a while back.  Someone was
proposing that we switch locals on the fly to provide i18n messages that are
useful to the end user.  My response to that was that we are writing server
code and IMHO application writers are going to want to catch these nasty
exceptions, maybe save state, and print out a nicer message with an
explanation as to how to proceed; while it does have its place, none of this
has any business being in server software.  Also, anyone who has ever had to
deal w/ product managers when writing an application will know that they
will not like whatever nice message we on the Geronimo cook up; it's not in
a product manager's nature to be happy with the way that things are. ;)

My point is that we should focus on a single locale to provide i18n messages
for the developers that are writing applications on our server.  Let's keep
it simple.  I am very concerned by some of the Byzantine constructs, no
offence meant, that are being discussed.


Regards,
Alan








---------------------------------------------------------------- 
      Visit our Internet site at http://www.reuters.com 

Get closer to the financial markets with Reuters Messaging - for more
information and to register, visit <http://www.reuters.com/messaging> 

Any views expressed in this message are those of  the  individual sender,
except  where  the sender specifically states them to be the views of The
Reuters Group.