cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Fagerstrom (JIRA)" <>
Subject [jira] Commented: (COCOON-1765) Logging
Date Sun, 02 Sep 2007 21:13:19 GMT


Daniel Fagerstrom commented on COCOON-1765:

Pax logging supports all major logging framework in an OSGi friendly way. Currently I just
use it as an (better) implementation of Commons Logging. All the classloading tricks of the
ordinary Commons Logging implementation makes it frustrating to use in an OSGi environment.

The point with using the Pax OSGi logging service from OPS4J in combination with the Commons
Logging implementation would be that the logging output would be available though the API
of the OSGi logging service. But at this point I don't know whether that would be useful or
not, so it can wait.

> Logging
> -------
>                 Key: COCOON-1765
>                 URL:
>             Project: Cocoon
>          Issue Type: New Feature
>          Components: - OSGi integration
>            Reporter: Reinhard Poetz
> [...] But my main thoughts is that logging need to be a centralized service, common for
all blocks (separate logging solutions for each block would be a pain).
> The logging implementation is contained in a block (that is installed early) and makes
the logger available as a service that other block can get through the service manager. This
way the logging implementation is chosen by the choice of logging block. Observe that I only
is talking about the blocks fw, within a block an ordinary ECM can be set up and it will inject
the logger in its managed objects through the usual Avalon style.
> Using the same logger interface everywhere is also practical I guess we continue to use
the o.a.avalon.framework.logger.Logger one. 
> (by Daniel Fagerstrom:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message