Should the class of ContextJNDISelector implement the interface of RepositorySelectorEx?

Hi, For 1.3, I was using the ContextJNDISelector and noticed that it didn't implement the interface of RepositorySelectorEx. That caused the ContextDetachingSCL to skip the condition of "(repositorySelector instanceof RepositorySelectorEx)" in the method of contextDestroyed. I would appreciate a

Re: Tailing capability for VFS log Receiver in Chainsaw

Well I'm really glad someone has taken an interest in Chainsaw. The VFS tailing feature of ssh is personally one I'd love, because we could really use it here at Aconex. Along that note, and to get you thinking (and planning for our Logging setup here at Aconex), that the VFS receiver with

DO NOT REPLY [Bug 41934] - DailyRollingFileAppender must chang as below

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 41934] New: - DailyRollingFileAppender must chang as below

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Tailing capability for VFS log Receiver in Chainsaw

Hi paul, It seems like you are really busy these days, anyway thank you very much for your interest... ~Isuru On 3/23/07, Paul Smith <[EMAIL PROTECTED]> wrote: I've applied to be a mentor as well. Not sure if an Apache org admin needs to 'bless' us. Scott, thanks for updating the Wiki. I

Re: Tailing capability for VFS log Receiver in Chainsaw

I've applied to be a mentor as well. Not sure if an Apache org admin needs to 'bless' us. Scott, thanks for updating the Wiki. I swear the hours in a day are being consumed faster these days. On 22/03/2007, at 5:38 PM, Scott Deboy wrote: Added to the wiki and applied as a mentor.

DO NOT REPLY [Bug 13099] - DOMConfigurator ignores category factory setting

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Debugging Log4J itself

I know there is log4j.debug... but that seems to only switch on the configuration initialization (just Joran in particular). Appenders and various other components of Log4j can *themselves* log (via ComponentBase.getLogger()) but I don't know how to configure Log4j to configure that. Any ideas?

Proposed Change to LoggingEvent.java

Hi Guys, Due to a requirement for a project I am working on, we recently made a small change to the log4j source file spi/LoggingEvent.java. We needed to pass in custom message objects when creating a log event, log those events over the SocketAppender, and write custom Appenders to deal with

Proposals for jmx package

Hi all, For better managing log4j, I propose add feature: - List all available loggers thru jmx And fix bug - Correct threshold attribute type of HierarchyDynamicMBean mbean. Now MBeanAttributeInfo return String type for this attribute, but actually returned type of the attribute is Level. htt