On Tue, 16 Jul 2002, Andy Clark wrote:
> ...
> public String formatMessage(Locale locale,
> String key, Object[] args) {
> StringBuffer str = new StringBuffer();
> str.append(key);
> int length = args != null ? args.length : 0;
> for (int i = 0; i < length; i++) {
> str.append('\t');
> str.append(String.valueOf(args[i]));
> }
> return str.toString();
> }
> ...
>
> Would this solve your problem?
my concern originally was that error string match based error
classification in ErrorHandler (or anywhere else) is inherently fragile.
when you base the classification on error strings the error messages
effectively become a part of the API and when someone changes the error
message (even a little bit) the application breaks (happened to me between
2.0.1 and 2.0.2).
i'm not sure whether i understood your code example entirely (i'm still a
Xerces novice) but i can't see how the code addresses that concern.
best regards,
--
aspa
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
