Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Wed, 27 Apr 2011 09:17:05 +0000 (UTC)
From: "Achim Nierbeck (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <747207484.5391.1303895825582.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <124461838.18901.1301406965857.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (KARAF-543) Add manual section around log custom
 appenders
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/KARAF-543?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13025=
684#comment-13025684 ]=20

Achim Nierbeck commented on KARAF-543:
--------------------------------------

A custom appender usually is in need of a Appender class which is only avai=
lable from the bundle in question, therefore a service solution is not real=
ly possible, and fragment bundles are meant to be used that way. What you d=
o here is to improve the standard with enhancements.=20

> Add manual section around log custom appenders
> ----------------------------------------------
>
>                 Key: KARAF-543
>                 URL: https://issues.apache.org/jira/browse/KARAF-543
>             Project: Karaf
>          Issue Type: Task
>          Components: documentation
>            Reporter: Jean-Baptiste Onofr=C3=A9
>             Fix For: 2.2.2, 3.0.0
>
>
> To be able to add custom appenders to PAX Logging, a fragment bundle is r=
equired with:
> Fragment-Host =3D org.ops4j.pax.logging.pax-logging-service
> A section of the Karaf dev manual should document that.
> The PAX Logging wiki should be update as well (I will).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira