"Henning P. Schmiedehausen" <[EMAIL PROTECTED]> wrote on 12/10/2004 04:34:07 AM:Richard Sitze <[EMAIL PROTECTED]> writes:
<snip>
- Utility function to support formatting for other purposes (exception strings):
formatMessage(String messageID); formatMessage(String messageID, Object messageParam); formatMessage(String messageID, Object[] messageParams);
Strictly -1. This is not the scope of commons-logging! We could add this to some other commons project. Once we add non-logging functionality to commons-logging, people will start using this for non-logging related purposes.
The intent was to facilitate obtaining loggable error/warning information
to be logged AND use the same information in an exception.
However, you raise a very good point.
Other comments on this?
i agree with Henning: definitely out of scope for commons-logging.
(for reasons given previously) i do think that subsidiary artifacts are going to be needed to perform the actual rendering. i would much prefer utility methods to be exposed from classes in those artifacts. these artifacts might be separate components or optional artifacts within commons-logging.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
