Mateusz Nowakowski (JIRA)
Wed, 27 Jan 2010 06:33:56 -0800
No implementations available for PaxAppender --------------------------------------------
Key: PAXLOGGING-72
URL: http://issues.ops4j.org/browse/PAXLOGGING-72
Project: Pax Logging
Issue Type: Improvement
Components: Service
Affects Versions: 1.4
Environment: WinXp, Fuse 4.2 RC1
Reporter: Mateusz Nowakowski
Assignee: Niclas Hedhman
Currently it is not possible to use own appender based on log4j using existing
PaxLoggingConfigurator. It is really strange because PaxLoggingConfigurator is
based on log4j appenders.
There can be used only PaxAppender implementation, but none is available.
There are two solutions to solve the problem. Both are bad.
- create own appender based on log4j appender and attach it via Fragment-Host
mechanism to Pax Logging Service bundle -- bad solution, because current
PaxLoggingConfigurator do not support error handlers etc (I've already created
PAXLOGGING-71 for it)
- write PaxAppender implementation which aggregates any log4 appender - bad,
because it requires an additional log4j bundle in the application (Pax Logging
exports only two log4j packages without most of log4j code, especially without
appenders), what is more it is a performance killer, because PaxAppender
implementation wraps some appender based on log4 appender, and PAX creates own
wrapper to return log4j appender from PaxAppender...
There are two complementary solution:
- PAXLOGGING-71
- PaxLoggingConfigurator or its AppenderTracker should track not only
PaxAppender but original log4j Appender. What is more all log4j packages should
be exported.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general