Bingo. And you can store static information, like bundle name, product
version and such, in the convenience class so it's available without having
to marshall it around.
> -----Original Message-----
> From: Michael Brennan [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 11, 2001 1:36 PM
> To: 'LOG4J Users Mailing List'
> Subject: RE: Convenience overloads in Category
>
>
> Another approach to achieve the same goal (and which doesn't violate
> internationalization guidelines) is to write a convenience
> class that wraps
> the funcionality of the MessageFormat class, and use that to
> construct the
> messages provided to log4j. That's what I do.
>
> > -----Original Message-----
> > From: Johnson, Clay [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, April 11, 2001 9:21 AM
> > To: 'LOG4J Users Mailing List'
> > Subject: RE: Convenience overloads in Category
> >
> >
> > Internationalization. Rule 1 is don't concatenate strings
> to compose
> > messages; it makes translation much more costly and invasive.
> > Ideally,
> > store messages in resource bundles, and if they are
> parameterized, use
> > MessageFormat.
> >
> > That is, if you need to be global, and I assume many log4j
> users do.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
