You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2009/04/03 11:54:12 UTC

[jira] Commented: (JCR-1695) Improve and promote spi-logger

    [ https://issues.apache.org/jira/browse/JCR-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695311#action_12695311 ] 

angela commented on JCR-1695:
-----------------------------

in agreement with marcel the original contributor of the spi-logger, i removed the sandbox/spi/spi-logger project 
at rev. 761589

> Improve and promote spi-logger
> ------------------------------
>
>                 Key: JCR-1695
>                 URL: https://issues.apache.org/jira/browse/JCR-1695
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-spi-commons, sandbox
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> The spi-logger is very useful for debugging an SPI implementation. However it only supports the RepositoryService interface. Other SPI interfaces are not supported. Also writing log information as string seems a bit restrictive to me. Finally it is not included in the jackrabbit-spi package which introduces an additional dependency for debugging. 
> I therefore suggest:
> - Add support for the other major SPI interfaces 
> - Replace the current way of logging a String to a Writer instance by a more versatile mechanism (i.e. clients have to provide an interface which consumes more structured log data). 
> - Provide some default implementation for the above mechanism (i.e. writing to a file, writing to a slf4j based logger, writing to the console...)
> - Promote this project to jackrabbit-spi

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