Likewise with the <log4net nullText="NULL-TEXT" notAvailableText="NOT-AVAILABLE-TEXT">, if these are set on the Repository then they should be repository specific. They could be stored in the Repository.Properties collection, but we would need to make sure that everything that needed the text knows which repository it is attached to, which isn't a bad thing, maybe ActivateOptions should be changed to pass in the Repository (we can do this without breaking existing APIs by adding an IOptionHandler2 interface).
Nicko > -----Original Message----- > From: Ron Grabowski (JIRA) [mailto:[EMAIL PROTECTED] > Sent: 04 November 2005 03:01 > To: log4net-dev@logging.apache.org > Subject: [jira] Created: (LOG4NET-55) Allow default null > text,"(null)", and default not available text, "NOT > AVAILABLE", to be configurable. > > Allow default null text,"(null)", and default not available > text, "NOT AVAILABLE", to be configurable. > -------------------------------------------------------------- > ---------------------------------------- > > Key: LOG4NET-55 > URL: http://issues.apache.org/jira/browse/LOG4NET-55 > Project: Log4net > Type: Improvement > Reporter: Ron Grabowski > Priority: Trivial > > > "(null)" and "NOT AVAILABLE" are not settable by the user. > Allow them to be settable via AppSettings keys: > > <add key="log4net.NullText" value="NULL-TEXT" /> <add > key="log4net.NotAvailableText" value="NOT-AVAILABLE-TEXT" /> > > or attributes on the log4net node: > > <log4net nullText="NULL-TEXT" notAvailableText="NOT-AVAILABLE-TEXT"> > ... > </log4net> > > or in code: > > log4net.Util.SystemInfo.NullText = "NULL-TEXT"; > log4net.Util.SystemInfo.NotAvailableText = "NOT-AVAILABLE-TEXT"; > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the > administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > >
