[
https://issues.apache.org/jira/browse/COCOON-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524447
]
Ralph Goers commented on COCOON-1765:
-------------------------------------
Daniel, all you did was repeat back what I said. It hasn't answered my concern.
In Cocoon 2.1 we use the Avalon logger API. We provide a couple of
implementation but anyone can write an implementation of this API to plug in
their own logging framework (as I have done).
As I understand the pages referenced above PAX will bind the client using a
particular API with the implementation of that API in a separate bundle. So it
looks to me that if Cocoon used the log4j api that it would be tied to the
log4j pax bundle, which is unacceptable. If this is correct then it is a
requirement that Cocoon 2.2 continue to use an abstract logging api such as the
Avalon logger.
Is this clear or do I misunderstand what PAX does?
> 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.
