From 64455161af4b9a455aa95b96f3869015e4b8ef77 Mon Sep 17 00:00:00 2001 From: Raman Gupta Date: Tue, 31 Jan 2012 13:45:08 -0500 Subject: [PATCH] Update manual/src/main/webapp/users-guide/logging-system.conf --- manual/src/main/webapp/users-guide/logging-system.conf | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/manual/src/main/webapp/users-guide/logging-system.conf b/manual/src/main/webapp/users-guide/logging-system.conf index 3ff6da60da0..f125e7047b7 100644 --- a/manual/src/main/webapp/users-guide/logging-system.conf +++ b/manual/src/main/webapp/users-guide/logging-system.conf @@ -1,4 +1,3 @@ - h1. Logging system Karaf provides a powerful logging system based on [OPS4j Pax Logging|http://team.ops4j.org/wiki/display/paxlogging/Pax+Logging]. @@ -174,4 +173,10 @@ Bundle-SymbolicName: org.mydomain.myappender Fragment-Host: org.ops4j.pax.logging.pax-logging-service ... -Now you can use the appender in your log4j config file like shown in the config examples above. +Copy the new appender fragment into the ${karaf.home}/system directory. Karaf uses a virtual maven repository to access resources in the system +directory, so the jar path should use the standard maven groupId/artifactId/version/ convention, where the groupId is a directory structure. + +Edit ${karaf.home}/etc/startup.properties and add the new fragment bundle to the list before the pax-logging-service bundle. + +Restart karaf with a clean run to reload the system bundles, and now you can use the appender in your log4j config file like shown in the config +examples above.