[EMAIL PROTECTED]: Project logging-log4j (in module logging-log4j) failed

2005-01-05 Thread noreply
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project logging-log4j has an issue affecting its community integration. This issue affect

RE: [POLL] Component and ComponentBase

2005-01-05 Thread Ceki Gülcü
Mark, As I understand it, a marker interface does not have methods. Since Component has one method, namely setLoggerRepository(), it is not a marker interface by definition. The Appender interface extends the Component interface. So when you get a handle on an object implementing the Appender inter

DO NOT REPLY [Bug 31458] - DailyRollingFileAppender fails with mult load-balancing JVMs under WAS

2005-01-05 Thread bugzilla
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 17498] - Logging inconsistencies using DailyRollingFileAppender

2005-01-05 Thread bugzilla
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

cvs commit: logging-log4j build.xml

2005-01-05 Thread ceki
ceki2005/01/05 08:50:41 Modified:.build.xml Log: The log4j.jar target would not run because the delete target could not delete the log4j-VERSION.jar file. This occurs because the build.chainsaw target in the build-chainsaw.xm ant file refers to log4j.jar through the

cvs commit: logging-log4j build-chainsaw.xml

2005-01-05 Thread ceki
ceki2005/01/05 08:50:53 Modified:.build-chainsaw.xml Log: The log4j.jar target would not run because the delete target could not delete the log4j-VERSION.jar file. This occurs because the build.chainsaw target in the build-chainsaw.xm ant file refers to log4j.jar th

cvs commit: logging-log4j build.xml

2005-01-05 Thread ceki
ceki2005/01/05 08:56:15 Modified:.build.xml Log: Indentation changes only. Revision ChangesPath 1.131 +144 -143 logging-log4j/build.xml Index: build.xml === RCS file: /home/cvs/loggi

Re: [POLL] Component and ComponentBase

2005-01-05 Thread Curt Arnold
At this point, the [POLL] in the subject is misleading since the changes have been started (possibly finished) in the CVS due to an accidental build breakage when some of the changes slipped in. I don't think anyone is advocating backing them out, but I do have reservations that I haven't had

cvs commit: logging-log4j build-chainsaw.xml

2005-01-05 Thread ceki
ceki2005/01/05 09:03:34 Modified:.build-chainsaw.xml Log: indentations changes only Revision ChangesPath 1.3 +113 -111 logging-log4j/build-chainsaw.xml Index: build-chainsaw.xml ===

Re: [POLL] Component and ComponentBase

2005-01-05 Thread Ceki Gülcü
Sounds reasonable. At 06:00 PM 1/5/2005, you wrote: At this point, the [POLL] in the subject is misleading since the changes have been started (possibly finished) in the CVS due to an accidental build breakage when some of the changes slipped in. I don't think anyone is advocating backing them

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

2005-01-05 Thread ceki
ceki2005/01/05 09:16:11 Modified:src/java/org/apache/log4j/joran/util JoranDocument.java src/java/org/apache/log4j/joran JoranConfigurator.java Log: JoranDocument now conform to the log4j internal logging guidelines. Revision ChangesPath 1.5 +21 -

cvs commit: logging-log4j/src/java/org/apache/log4j/joran/util JoranDocument.java

2005-01-05 Thread ceki
ceki2005/01/05 09:18:00 Modified:src/java/org/apache/log4j/joran/util JoranDocument.java Log: Making JoranDocument conform to the log4j internal logging guidelines. Revision ChangesPath 1.6 +1 -2 logging-log4j/src/java/org/apache/log4j/joran/util/JoranDocu

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

2005-01-05 Thread ceki
ceki2005/01/05 09:27:57 Modified:src/java/org/apache/log4j/net MulticastAppender.java Log: - Removed non-default constructors. - Changed getAddressByName method to become instance method instead of static. Revision ChangesPath 1.8 +2 -21 logging-log4j/src

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

2005-01-05 Thread ceki
ceki2005/01/05 09:42:09 Modified:src/java/org/apache/log4j/net SMTPAppender.java Log: SMTPAppender now takes advantage of the poweful new features in Joran, in particular the capabilty to configure appeder sub-components. Revision ChangesPath 1.44 +30 -36 lo

RE: cvs commit: logging-log4j/src/java/org/apache/log4j/net SMTPAppender.java

2005-01-05 Thread Scott Deboy
Thanks Ceki - I was hoping this is where it would end up. Does this use implicit actions? I see that selfInitialize in o.a.l.joran.JoranConfigurator registers a number of rules, but I don't see anything referring to TriggeringEventEvaluators. Scott -Original Message- From: [EMAIL

RE: cvs commit: logging-log4j/src/java/org/apache/log4j/net SMTPAppender.java

2005-01-05 Thread Ceki Gülcü
At 06:51 PM 1/5/2005, you wrote: Thanks Ceki - I was hoping this is where it would end up. Does this use implicit actions? Yes, it does. I see that selfInitialize in o.a.l.joran.JoranConfigurator registers a number of rules, but I don't see anything referring to TriggeringEventEvaluators. Conside

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

2005-01-05 Thread ceki
ceki2005/01/05 10:27:15 Modified:src/java/org/apache/joran/action NestComponentIA.java Log: Pass repository information along to sub-components. Revision ChangesPath 1.16 +4 -1 logging-log4j/src/java/org/apache/joran/action/NestComponentIA.java Index:

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

2005-01-05 Thread ceki
ceki2005/01/05 10:29:05 Modified:src/java/org/apache/joran/action NestComponentIA.java Log: Pass repository information along to sub-components. Revision ChangesPath 1.17 +2 -0 logging-log4j/src/java/org/apache/joran/action/NestComponentIA.java Index:

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

2005-01-05 Thread ceki
ceki2005/01/05 10:37:54 Modified:src/java/org/apache/log4j/net SocketAppender.java Log: Making SocketAppender to the log4j internal logging guidelines. Revision ChangesPath 1.25 +63 -71 logging-log4j/src/java/org/apache/log4j/net/SocketAppender.java Inde

cvs commit: logging-log4j/src/java/org/apache/log4j/jdbc package.html JDBCAppender.java

2005-01-05 Thread ceki
ceki2005/01/05 11:15:34 Removed: src/java/org/apache/log4j/jdbc package.html JDBCAppender.java Log: Removed o.a.l.jdbc. It had been deprecated for a long time. - To unsubscribe, e-mail: [

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

2005-01-05 Thread Curt Arnold
Instead of actionData.nestedComponent = Loader.loadClass(className).newInstance(); - + if(actionData.nestedComponent instanceof Component) { +((Component) actionData.nestedComponent).setLoggerRepository(this.repository); + } Could you do something like: actionD

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

2005-01-05 Thread Ceki Gülcü
At 08:28 PM 1/5/2005, you wrote: Instead of actionData.nestedComponent = Loader.loadClass(className).newInstance(); - + if(actionData.nestedComponent instanceof Component) { +((Component) actionData.nestedComponent).setLoggerRepository(this.repository); + } Cou