[ https://issues.apache.org/jira/browse/COCOON-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524437 ]
Daniel Fagerstrom commented on COCOON-1765:
-------------------------------------------
When I look at the same link I find client code examples for Log4J, Jakarta Commons Logging, SLF4J, Avalon Logging, JDK Logging, Knopflerfish Log and Pax Logging in the client code section. Also they are moving their documentation to Confluence, a newer version of the document can be found here http://wiki.ops4j.org/confluence/display/ops4j/Pax+Logging.
> Logging
> -------
>
> Key: COCOON-1765
> URL: https://issues.apache.org/jira/browse/COCOON-1765
> 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: http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=113889468124728&w=2)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.