You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2007/06/27 10:27:26 UTC
[jira] Resolved: (JCR-985) [PATCH] refactor access to SAXParser and
log which parser class is used
[ https://issues.apache.org/jira/browse/JCR-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg resolved JCR-985.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.1
Assignee: Felix Meschberger
fixed in svn r551090 by applying bertrand's patch.
thanks for the patch!
> [PATCH] refactor access to SAXParser and log which parser class is used
> -----------------------------------------------------------------------
>
> Key: JCR-985
> URL: https://issues.apache.org/jira/browse/JCR-985
> Project: Jackrabbit
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.3.1
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
> Priority: Minor
> Fix For: 1.3.1
>
> Attachments: SAXParserProvider.patch
>
>
> This parser collects code that was duplicated in the SessionImpl and WorkspaceImpl class to initialize the SAXParser.
> Also, the actual SAXParser class being used is logged (once only) to make it easier to debug problems like JCR-984.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.