cocoon-dev mailing list archives

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


Ralph Goers commented on COCOON-1765:

I looked at the link posted by Reinhard.  While the doc clealy states that it supports several
different logging frameworks the examples still have the client code using a particular implementation.
In other words, it looks to me like I could create my own PAX implementation but if the client
has coded to log4j's api then my implementation wouldn't work.  Please correct me if I misunderstand
how it works, but if that is the case then it doesn't meet the requirements.

> 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