--- [EMAIL PROTECTED] wrote:
On Wed, 21 Mar 2001, Mel Martinez wrote:
StringManager's getString() currently deals with
the
MissingResourceException by simply returning a
String
consisting of a warning message about not being
able
to find the particular key. I don't think that is
Would the following be an acceptable solution?
We change the
Constants.message(key,args,verbosityLevel) method
behavior so that if getString(key,args) throws
a missing resource exception that it logs using the
key itself as the log message. Note that this would
also require changing the
On Wed, 21 Mar 2001, Mel Martinez wrote:
Would the following be an acceptable solution?
We change the
Constants.message(key,args,verbosityLevel) method
behavior so that if getString(key,args) throws
a missing resource exception that it logs using the
key itself as the log message. Note
--- [EMAIL PROTECTED] wrote:
On Wed, 21 Mar 2001, Mel Martinez wrote:
Would the following be an acceptable solution?
We change the
Constants.message(key,args,verbosityLevel) method
behavior so that if getString(key,args) throws
a missing resource exception that it logs using
the
--- [EMAIL PROTECTED] wrote:
On Wed, 21 Mar 2001, Mel Martinez wrote:
Would the following be an acceptable solution?
We change the
Constants.message(key,args,verbosityLevel) method
behavior so that if getString(key,args) throws
a missing resource exception that it logs using
the
On Wed, 21 Mar 2001, Mel Martinez wrote:
StringManager's getString() currently deals with the
MissingResourceException by simply returning a String
consisting of a warning message about not being able
to find the particular key. I don't think that is
correct behavior. I think it should
