You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by ps...@apache.org on 2006/02/24 03:43:57 UTC
svn commit: r380313 - in /logging/chainsaw/trunk:
src/java/org/apache/log4j/chainsaw/ src/java/org/apache/log4j/chainsaw/help/
src/java/org/apache/log4j/chainsaw/version/
zeroconf/org/apache/log4j/chainsaw/zeroconf/
Author: psmith
Date: Thu Feb 23 18:43:55 2006
New Revision: 380313
URL: http://svn.apache.org/viewcvs?rev=380313&view=rev
Log:
Activated the ZeroConf plugin, i've done testing locally and it appears to work very well.
Only thing now is for someone else to try it...
Modified:
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/LogUI.java
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html
logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java
logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html
Modified: logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/LogUI.java
URL: http://svn.apache.org/viewcvs/logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/LogUI.java?rev=380313&r1=380312&r2=380313&view=diff
==============================================================================
--- logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/LogUI.java (original)
+++ logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/LogUI.java Thu Feb 23 18:43:55 2006
@@ -477,15 +477,15 @@
// pluginRegistry.addPlugin(cc);
// cc.activateOptions();
-// try {
-// Class pluginClass = Class.forName("org.apache.log4j.chainsaw.zeroconf.ZeroConfPlugin");
-// Plugin plugin = (Plugin) pluginClass.newInstance();
-// pluginRegistry.addPlugin(plugin);
-// plugin.activateOptions();
-// MessageCenter.getInstance().getLogger().info("Looks like ZeroConf stuff is available... WooHoo!");
-// } catch (Throwable e) {
-// MessageCenter.getInstance().getLogger().error("Doesn't look like ZeroConf is available", e);
-// }
+ try {
+ Class pluginClass = Class.forName("org.apache.log4j.chainsaw.zeroconf.ZeroConfPlugin");
+ Plugin plugin = (Plugin) pluginClass.newInstance();
+ pluginRegistry.addPlugin(plugin);
+ plugin.activateOptions();
+ MessageCenter.getInstance().getLogger().info("Looks like ZeroConf stuff is available... WooHoo!");
+ } catch (Throwable e) {
+ MessageCenter.getInstance().getLogger().error("Doesn't look like ZeroConf is available", e);
+ }
}
private void setupReceiverPanel() {
Modified: logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html
URL: http://svn.apache.org/viewcvs/logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html?rev=380313&r1=380312&r2=380313&view=diff
==============================================================================
--- logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html (original)
+++ logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/help/release-notes.html Thu Feb 23 18:43:55 2006
@@ -10,6 +10,11 @@
<b>NOTE:</b> The mechanism and format used to persist settings in Chainsaw is subject to change during this alpha phase. If you are experiencing problems displaying events in Chainsaw, please delete everything in the $user.dir/.chainsaw directory.
<br>
<h1>1.99.99</h2>
+<h2>24 February 2006</h2>
+<ul>
+<li>Added ZeroConf plugin, allowing simple point-n-click connection to detected appenders. See the <B>ZeroConf</B> tab inside
+Chainsaw.</li>
+</ul>
<h2>20 February 2006</h2>
<ul>
<li>Using a different file name to load and save global settings (from chainsaw.xml to chainsaw.settings.xml). <b>NOTE:</b>Users will need to re-apply their application-wide settings or copy chainsaw.xml to chainsaw.settings.xml.</li>
Modified: logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java
URL: http://svn.apache.org/viewcvs/logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java?rev=380313&r1=380312&r2=380313&view=diff
==============================================================================
--- logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java (original)
+++ logging/chainsaw/trunk/src/java/org/apache/log4j/chainsaw/version/VersionManager.java Thu Feb 23 18:43:55 2006
@@ -10,7 +10,7 @@
private static final VersionManager instance = new VersionManager();
- private static final String VERSION_INFO = "1.99.99 (20 February 2006)";
+ private static final String VERSION_INFO = "1.99.99 (24 February 2006)";
public static final VersionManager getInstance() {
return instance;
Modified: logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html
URL: http://svn.apache.org/viewcvs/logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html?rev=380313&r1=380312&r2=380313&view=diff
==============================================================================
--- logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html (original)
+++ logging/chainsaw/trunk/zeroconf/org/apache/log4j/chainsaw/zeroconf/ZeroConfPlugin.html Thu Feb 23 18:43:55 2006
@@ -31,9 +31,29 @@
<h2>Interesting... So what do I need to use ZeroConf with Chainsaw & log4j?</h2>
<p>
The log4j team has created an additional JAR file that can be added to your existing
-application to enable ZeroConf configuration. You just need to download the <code>log4j-zeroconf.jar</code> and the JmDNS package. Then change your references from <code>SocketHubAppender</code>
-to <code>ZeroConfSocketHubAppender</code>. (We recommend you change the 'name' propety from it's default to make it easy for you to use, other
+application to enable ZeroConf configuration. You just need to download the <code>log4j-zeroconf.jar</code> and the JmDNS package and add
+both JARs to your application's classpath. </p>
+<p> Then change your references from <code>SocketHubAppender</code>
+to <code><b>ZeroConf</b>SocketHubAppender</code>. (We recommend you change the 'name' propety from it's default to make it easy for you to use, other
wise it's name will appear as the default 'SocketHubAppender').
+</p>
+<p>You're log4j.xml configuration file could be as simple as this:</p>
+<pre>
+<log4j:configuration debug="false" threshold="debug" xmlns:log4j="http://jakarta.apache.org/log4j/>
+ <appender name="zeroconf" class="org.apache.log4j.net.ZeroConfSocketHubAppender">
+ <param name="Name" value="MyZeroConfSockeHubAppender" />
+ </appender>
+ <!--ROOT Logger-->
+ <root>
+ <level value="INFO" />
+ <appender-ref ref="zeroconf" />
+ </root>
+</log4j:configuration>
+</pre>
+<p>
+Once you have started your application using this new appender, then from within Chainsaw, the ZeroConf tab will show detected
+applications. You can simply double click on the detected app, and Chainsaw will connect a Receiver to it. You can even tick the "Auto-Connet"
+check box, and next time Chainsaw see's this application, it will automatically connect to it.
</p>
<h2>Cool... But I have some applications that use log4j 1.2.x. Will it still work?</h2>
<p>Yes. We have designed a backward compatible mechanism to expose log4j 1.2.x SocketHubAppender so that Chainsaw can detect it automatically.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org