RE: Best practices for localization of exception messages

2004-09-09 Thread bmf5
"Jim Barrows" <[EMAIL PROTECTED]> wrote on 09/09/2004 01:23:12 PM: snip > > Yep, that's it. I know what went wrong in general, and can drill > down to the specifics if I need to for error reporting. > In general I always at least include the PK in a message, even for > an exception that

Re: Best practices for localization of exception messages

2004-09-09 Thread bmf5
Brett Connor <[EMAIL PROTECTED]> wrote on 09/09/2004 02:03:00 PM: > [EMAIL PROTECTED] wrote: > > >Brett Connor <[EMAIL PROTECTED]> wrote on 09/09/2004 12:22:39 PM: > > > > > > > > Yep. The error code in whatever form it is in (depending on your company > standards and convesions) can be u

Re: Best practices for localization of exception messages

2004-09-09 Thread Brett Connor
[EMAIL PROTECTED] wrote: Brett Connor <[EMAIL PROTECTED]> wrote on 09/09/2004 12:22:39 PM: Taking a step back though, the locale is required for presentation only (in this example), it belongs in the view rather than any business components. It is not the job of the business layer to be decidin

RE: Best practices for localization of exception messages

2004-09-09 Thread Jim Barrows
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 09, 2004 10:16 AM > To: Struts Users Mailing List > Subject: RE: Best practices for localization of exception messages > > > > > > > > >

RE: Best practices for localization of exception messages

2004-09-09 Thread bmf5
"Jim Barrows" <[EMAIL PROTECTED]> wrote on 09/09/2004 01:00:11 PM: > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Thursday, September 09, 2004 9:52 AM > > To: Struts Users Mailing List >

RE: Best practices for localization of exception messages

2004-09-09 Thread Jim Barrows
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 09, 2004 9:52 AM > To: Struts Users Mailing List > Subject: RE: Best practices for localization of exception messages > > > > > > > snip > &g

Re: Best practices for localization of exception messages

2004-09-09 Thread bmf5
Brett Connor <[EMAIL PROTECTED]> wrote on 09/09/2004 12:22:39 PM: > [EMAIL PROTECTED] wrote: > > > >I've started using chained exceptions per the suggestion in Struts in > >Action. I'm also trying to localize the messages. What I'm not sure of is > >the best way to get the locale down to

RE: Best practices for localization of exception messages

2004-09-09 Thread bmf5
snip > I'll catch an SQLException, put it in a DAOFailureException ( which > inherits from DaoException typically), throw it. BO catches, rolls > it into an DataStoreFatalApplicationException (which inherits from > FatalApplicationExcpetion, which inherits from BOException), and > throws it

Re: Best practices for localization of exception messages

2004-09-09 Thread Brett Connor
[EMAIL PROTECTED] wrote: I've started using chained exceptions per the suggestion in Struts in Action. I'm also trying to localize the messages. What I'm not sure of is the best way to get the locale down to the lower layers where the chained exception originates. I haven't passed the session or

RE: Best practices for localization of exception messages

2004-09-09 Thread Jim Barrows
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 09, 2004 9:01 AM > To: [EMAIL PROTECTED] > Subject: Best practices for localization of exception messages > > > > > > > > I'm learn

Best practices for localization of exception messages

2004-09-09 Thread bmf5
I'm learning and building as I go and have run into a situation that I'm not sure if I'm handling right. I've started using chained exceptions per the suggestion in Struts in Action. I'm also trying to localize the messages. What I'm not sure of is the best way to get the locale down to the