> > The configuration for the event "sink": > > > > <?xml version="1.0" encoding="UTF-8" ?> > > <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd"> > > > > <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"; > > debug="true"> > > <!-- > > <appender name="stdout" class="org.apache.log4j.ConsoleAppender"> > > <layout class="org.apache.log4j.PatternLayout"> > > <param name="ConversionPattern" value="%d{ABSOLUTE} %c{1}: > > %m%n"/> > > </layout> > > </appender> > > --> > > > > <appender name="A1" class="org.apache.log4j.FileAppender"> > > <param name="File" value="output/filters.PluginsTest.txt" /> > > <param name="Append" value="false" /> > > > > <layout class="org.apache.log4j.PatternLayout"> > > <param name="ConversionPattern" > > value="%d{ABSOLUTE} %c: %m%n"/> > > </layout> > > </appender> > > > > <plugin name="SocketReceiver" > > class="org.apache.log4j.net.SocketReceiver"> > > <param name="Port" value="5000"/> > > </plugin> > > > > <root> > > <level value="debug"/> > > <appender-ref ref="A1" /> > > </root> > > </log4j:configuration> > > I can't seem to find the filters.PluginsTest.txt file in HEAD.? I'll need > to read up more about the plugin's tag and what it means to fully > grasp the > above, but I can guess that somehow the SocketReceiver will also > receive the > events coming from the Root logger via the appender-ref, but I'm not clear > where/how that relationship is defined (possibly in the > pluginsTest.txt file > I can't seem to find?).
The FileAppender will write to the a file named output/filters.PluginsTest.txt, so it won't be in cvs or anything. It is just a left over name I had in the example I used to test the receiver. The way this works is: 1) The receiver receives a remote event. It "posts" the event to the logger repository. 2) The logger repository sends the event to all configured appenders it should be seen by. In this case, the A1 appender attached to the root logger will be given the event. 3) The A1 appender "appends" the event to the file output/filters.PluginsTest.txt. If there were other appenders defined in the configuration, they would get a chance to append the event too, depending on the configuration (ie an appender might be attached to a specific logger, and the event might not be for that logger). Again, this will give you some measure of configuration control as to which events get logged to the mythical ChainsawAppender. Hope that makes sense. -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
