You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2007/05/22 12:29:16 UTC
[jira] Resolved: (JCR-634) Log / trace wrapper for the JCR API
[ https://issues.apache.org/jira/browse/JCR-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-634.
-------------------------------
Resolution: Fixed
Assignee: Jukka Zitting
Committed the contributed code to contrib/jcrlog in revision 540521. Thanks, and sorry for the long delay!
> Log / trace wrapper for the JCR API
> -----------------------------------
>
> Key: JCR-634
> URL: https://issues.apache.org/jira/browse/JCR-634
> Project: Jackrabbit
> Issue Type: New Feature
> Reporter: Thomas Mueller
> Assigned To: Jukka Zitting
> Attachments: jcrlog.zip
>
>
> I have implemented the log / trace mechanism for the JCR API. A short summary:
> - A wrapper for a Repository. All other objects that where created directly or indirectly (Session, Node and so on) are wrapped as well.
> - The wrappers log all JCR method calls to a file and call the underlying methods.
> - Return values and calling method / line number can be logged as well (optional).
> - The log file itself is mainly Java source code and can be compiled and run.
> - Included is a player to re-play log files (for example, if the log file is too big to be compiled).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.