cvs commit: logging-log4j/src/java/org/apache/log4j/joran/action ActionConst.java

sdeboy 2004/01/16 16:12:47 Modified:src/java/org/apache/log4j/selector ContextJNDISelector.java src/java/org/apache/log4j/joran/action ActionConst.java Log: Character fixes - replaced Ceki's uumlauts with the escape, removed hidden bad character from ActionConst - th

cvs commit: logging-log4j/src/java/org/apache/log4j/net MulticastAppender.java XMLSocketReceiver.java

sdeboy 2004/01/16 15:49:03 Modified:src/java/org/apache/log4j/rule ExpressionRule.java ExpressionRuleContext.java src/java/org/apache/log4j/chainsaw LogPanel.java TableColorizingRenderer.java LogUI.java

RE: log4j jmx extension: we would like to participate

Return Receipt Your document: RE: log4j jmx extension: we would like to participate was received by: Paul Glezen/Austin/IBM at: 01/15/2004 22:03:55 PST

Re: log4j jmx extension: we would like to participate

Ceki Gülcü wrote: I would suggest that to work against the latest code from CVS not 1.2.8. Of course, we will work against the cvs-head. The reason why we used 1.2.8 is, we originally did not intended to adapt log4j. We just wanted to check the jmx extension of 1.2.8, which is the same as in the

RE: log4j jmx extension: we would like to participate

Thanks Ceki, good advice! -Original Message- From: Ceki Gülcü [mailto:[EMAIL PROTECTED] Sent: Friday, 16 January 2004 11:57 To: Log4J Developers List Subject: Re: log4j jmx extension: we would like to participate I would suggest that to work against the latest code from CVS not 1.2.8.

Re: log4j jmx extension: we would like to participate

I would suggest that to work against the latest code from CVS not 1.2.8. Your best chances to have the code integrated to a release is to supply small, humanely manageable patches. Large patches require a leap of faith which we are not always inclined to take. If you change the indentation of the c

Re: log4j jmx extension: we would like to participate

Hello What we have done so far is to patch the jmx extension of log4j 1.2.8 with the patch of Bill Rossi, as described by Ceki. This patch provides compatibility with jmx 1.2, primarily by adapting the existing sources according to the naming conventions of jmx 1.2. As soon as we have made som

Re: log4j jmx extension: we would like to participate

..good idea, please give me some time to check your suggestion. 'Peter Rob Butler wrote: JMX is an important feature for me as well in Log4j. One thing that may be simple to implement is JMX MBeans that directly update the Log4j configuration files, and then issues a reload request to Log4j. Lo

Re: log4j jmx extension: we would like to participate

Hi Andreas Wow, ok. I would appreciate your inputs. We will remain in contact. 'Peter Andreas Bothner [ MTN - Innovation Centre ] wrote: Hi Peter, I have read the same message. We are busy doing our first J2EE App Server implementation and I have been looking at the JMX API in order to write m

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw ChainsawCyclicBufferTableModel.java

sdeboy 2004/01/16 00:25:56 Modified:src/java/org/apache/log4j/chainsaw ChainsawCyclicBufferTableModel.java Log: Better handling of invalid expressions in refilter - performing notifications Revision ChangesPath 1.21 +4 -3 logging-log4j/

cvs commit: logging-log4j-sandbox/src/java/org/apache/log4j/jdbc JDBCReceiverBeanInfo.java JDBCReceiver.java

sdeboy 2004/01/16 00:12:06 Modified:src/java/org/apache/log4j/jdbc JDBCReceiver.java Added: src/java/org/apache/log4j/jdbc JDBCReceiverBeanInfo.java Log: jdbcreceiver now implementing pauseable (can be paused from chainsaw's receiver panel) added beaninfo class Revis

cvs commit: logging-log4j/src/java/org/apache/log4j/spi LoggingEventFieldResolver.java

sdeboy 2004/01/16 00:02:11 Modified:src/java/org/apache/log4j/chainsaw ChainsawCyclicBufferTableModel.java LoggerNameTreePanel.java src/java/org/apache/log4j/spi LoggingEventFieldResolver.java Log: Added null checks ch