Use org.rifidi.logging - Revision history

Bppause at 11:25, 18 September 2014

2014-09-18T11:25:13Z

Bppause at 11:24, 18 September 2014

2014-09-18T11:24:12Z

Matt: Reverted edits by Amesycyxa (Talk); changed back to last version by Kyle

2010-11-26T19:41:05Z

Reverted edits by Amesycyxa (Talk); changed back to last version by Kyle

Amesycyxa at 23:24, 23 November 2010

2010-11-23T23:24:35Z

Kyle at 15:06, 19 December 2008

2008-12-19T15:06:26Z

Kyle: New page: `org.rifidi.logging` is a bundle that provides a logging service for other bundles in the rifidi project. Specifically it provides org.apache.commons.logging and
2008-12-19T15:05:59Z

New page: <code>org.rifidi.logging</code> is a bundle that provides a logging service for other bundles in the rifidi project. Specifically it provides <cod>org.apache.commons.logging</code> and <c...

New page
<code>org.rifidi.logging</code> is a bundle that provides a logging service for other bundles in the rifidi project. Specifically it provides <cod>org.apache.commons.logging</code> and <code>org.apache.log4j</code>. Log4J relies on a file called <code>log4j.properties</code> to provide configuration information. The plugin itself does not have a <code>log4j.properties</code> folder in it. Instead, it relies on a OSGi bundle fragment to add one to the classpath.

To use it in another plugin:
# Make sure that the bundle is checked out in your workspace. You can either download the plugin from the <code>rep-external</code> svn repository, or you can use the binary from <code>org.rifidi.binary</code> along with a target platform.
# In the Manifest for your plugin, declare a package import of <code>org.apache.commons.logging</code>. Make sure that the minimum version is 1.0.4.
# In the run configuration:
## Make sure that <code>org.rifidi.logging</code> is checked.
## Make sure that only one log4J fragment is checked. If more than one is loaded, it is not defined which one will be used to configure log4j.
## Make sure that <code>org.apache.commons.logging</code> or <code>org.apache.log4j</code> is not being provided by a target platform. It is recommended that target platforms used by rifidi not contain either of these two bundles.

@@ Line 11: / Line 11: @@
 Default Configuration (Info and higher (no debug output)
+<pre>
 #Default level is INFO to avoid too much output from 3rd Party libraries
 log4j.rootLogger=INFO, stdout, fileappender
@@ Line 44: / Line 44: @@
 #log4j.appender.fileappender.layout=org.apache.log4j.PatternLayout
 #log4j.appender.fileappender.layout.ConversionPattern=%d{ABSOLUTE} %5p %c:%L - %m%n

← Older revision		Revision as of 11:24, 18 September 2014
Line 8:		Line 8:
	## Make sure that only one log4J fragment is checked. If more than one is loaded, it is not defined which one will be used to configure log4j.		## Make sure that only one log4J fragment is checked. If more than one is loaded, it is not defined which one will be used to configure log4j.
	## Make sure that <code>org.apache.commons.logging</code> or <code>org.apache.log4j</code> is not being provided by a target platform. It is recommended that target platforms used by rifidi not contain either of these two bundles.		## Make sure that <code>org.apache.commons.logging</code> or <code>org.apache.log4j</code> is not being provided by a target platform. It is recommended that target platforms used by rifidi not contain either of these two bundles.
		+	Note: Once a Rifidi application is exported teh Edge logging configuration is set in \server\config\logging.properties
		+
		+	Default Configuration (Info and higher (no debug output)
		+
		+	#Default level is INFO to avoid too much output from 3rd Party libraries
		+	log4j.rootLogger=INFO, stdout, fileappender
		+
		+	#Don't care about springframework info statements
		+	log4j.category.org.springframework=warn
		+	#Except for RMI info statements!
		+	log4j.category.org.springframework.remoting=info
		+
		+	#output from apache projects
		+	log4j.category.org.apache.mina=WARN
		+
		+	#Output from LLRP LTK
		+	log4j.category.org.llrp=WARN
		+
		+	#Output from Rifidi Edge Server core
		+	log4j.category.org.rifidi.edge.core.sensors.base.AbstractIPSensorSession=INFO
		+
		+	#log4j.category.org.apache=ALL
		+	#log4j.category.org.apache.commons.digester=INFO
		+
		+	#Set up Console appender
		+	log4j.appender.stdout=org.apache.log4j.ConsoleAppender
		+	log4j.appender.stdout.Target=System.out
		+	log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
		+	log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p %c:%L - %m%n
		+
		+	#Set up File Appender
		+	#log4j.appender.fileappender=org.apache.log4j.DailyRollingFileAppender
		+	#log4j.appender.fileappender.File=logs/edge.log
		+	#log4j.appender.fileappender.DatePattern='.'yyyy-MM-dd-HH-mm
		+	#log4j.appender.fileappender.layout=org.apache.log4j.PatternLayout
		+	#log4j.appender.fileappender.layout.ConversionPattern=%d{ABSOLUTE} %5p %c:%L - %m%n

@@ Line 1: / Line 1: @@
-=[http://asuxoqonyb.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
+<code>org.rifidi.logging</code> is a bundle that provides a logging service for other bundles in the rifidi project.  Specifically it provides <code>org.apache.commons.logging</code> and <code>org.apache.log4j</code>.  Log4J relies on a file called <code>log4j.properties</code> to provide configuration information. The plugin itself does not have a <code>log4j.properties</code> folder in it.  Instead, it relies on a OSGi bundle fragment to add one to the classpath.
-&lt;code&gt;org.rifidi.logging&lt;/code&gt; is a bundle that provides a logging service for other bundles in the rifidi project.  Specifically it provides &lt;code&gt;org.apache.commons.logging&lt;/code&gt; and &lt;code&gt;org.apache.log4j&lt;/code&gt;.  Log4J relies on a file called &lt;code&gt;log4j.properties&lt;/code&gt; to provide configuration information. The plugin itself does not have a &lt;code&gt;log4j.properties&lt;/code&gt; folder in it.  Instead, it relies on a OSGi bundle fragment to add one to the classpath.
 To use it in another plugin:
-# Make sure that the bundle is checked out in your workspace.  You can either download the plugin from the &lt;code&gt;rep-external&lt;/code&gt; svn repository, or you can use the binary from &lt;code&gt;org.rifidi.binary&lt;/code&gt; along with a target platform.
+# Make sure that the bundle is checked out in your workspace.  You can either download the plugin from the <code>rep-external</code> svn repository, or you can use the binary from <code>org.rifidi.binary</code> along with a target platform.
-# In the Manifest for your plugin, declare a package import of &lt;code&gt;org.apache.commons.logging&lt;/code&gt;.  Make sure that the minimum version is 1.0.4.
+# In the Manifest for your plugin, declare a package import of <code>org.apache.commons.logging</code>.  Make sure that the minimum version is 1.0.4.
 # In the run configuration:
-## Make sure that &lt;code&gt;org.rifidi.logging&lt;/code&gt; is checked.
+## Make sure that <code>org.rifidi.logging</code> is checked.
 ## Make sure that only one log4J fragment is checked.  If more than one is loaded, it is not defined which one will be used to configure log4j.
-## Make sure that &lt;code&gt;org.apache.commons.logging&lt;/code&gt; or &lt;code&gt;org.apache.log4j&lt;/code&gt; is not being provided by a target platform.  It is recommended that target platforms used by rifidi not contain either of these two bundles.
+## Make sure that <code>org.apache.commons.logging</code> or <code>org.apache.log4j</code> is not being provided by a target platform.  It is recommended that target platforms used by rifidi not contain either of these two bundles.

← Older revision		Revision as of 15:06, 19 December 2008
Line 1:		Line 1:
−	<code>org.rifidi.logging</code> is a bundle that provides a logging service for other bundles in the rifidi project. Specifically it provides <~~cod~~>org.apache.commons.logging</code> and <code>org.apache.log4j</code>. Log4J relies on a file called <code>log4j.properties</code> to provide configuration information. The plugin itself does not have a <code>log4j.properties</code> folder in it. Instead, it relies on a OSGi bundle fragment to add one to the classpath.	+	<code>org.rifidi.logging</code> is a bundle that provides a logging service for other bundles in the rifidi project. Specifically it provides <code>org.apache.commons.logging</code> and <code>org.apache.log4j</code>. Log4J relies on a file called <code>log4j.properties</code> to provide configuration information. The plugin itself does not have a <code>log4j.properties</code> folder in it. Instead, it relies on a OSGi bundle fragment to add one to the classpath.

	To use it in another plugin:		To use it in another plugin: