You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Dave Brosius (JIRA)" <ji...@apache.org> on 2008/04/11 05:56:04 UTC

[jira] Created: (JCR-1531) [PATCH] Add Column and line numbers to repository.xml parse exception messages

[PATCH] Add Column and line numbers to repository.xml parse exception messages
------------------------------------------------------------------------------

                 Key: JCR-1531
                 URL: https://issues.apache.org/jira/browse/JCR-1531
             Project: Jackrabbit
          Issue Type: Improvement
          Components: jackrabbit-core
    Affects Versions: core 1.4.2
            Reporter: Dave Brosius
            Priority: Trivial
             Fix For: 1.5
         Attachments: report_config_parse_error_position.patch

Code caught SAXExceptions when the an xml parsing exception occurred parsing the repository.xml. But catching SAXParseException (a subclass) allows access to column and line numbers of the problem. So also catch this exception and add this to the exception message to make it easier to fix errors.

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


[jira] Resolved: (JCR-1531) [PATCH] Add Column and line numbers to repository.xml parse exception messages

Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved JCR-1531.
-----------------------------------

    Resolution: Fixed

Committed patch after converting tabs to spaces.

Thank you for providing the patch.

svn revision: 647133

> [PATCH] Add Column and line numbers to repository.xml parse exception messages
> ------------------------------------------------------------------------------
>
>                 Key: JCR-1531
>                 URL: https://issues.apache.org/jira/browse/JCR-1531
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: core 1.4.2
>            Reporter: Dave Brosius
>            Priority: Trivial
>             Fix For: 1.5
>
>         Attachments: report_config_parse_error_position.patch
>
>
> Code caught SAXExceptions when the an xml parsing exception occurred parsing the repository.xml. But catching SAXParseException (a subclass) allows access to column and line numbers of the problem. So also catch this exception and add this to the exception message to make it easier to fix errors.

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


[jira] Updated: (JCR-1531) [PATCH] Add Column and line numbers to repository.xml parse exception messages

Posted by "Dave Brosius (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Brosius updated JCR-1531:
------------------------------

    Attachment: report_config_parse_error_position.patch

> [PATCH] Add Column and line numbers to repository.xml parse exception messages
> ------------------------------------------------------------------------------
>
>                 Key: JCR-1531
>                 URL: https://issues.apache.org/jira/browse/JCR-1531
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: core 1.4.2
>            Reporter: Dave Brosius
>            Priority: Trivial
>             Fix For: 1.5
>
>         Attachments: report_config_parse_error_position.patch
>
>
> Code caught SAXExceptions when the an xml parsing exception occurred parsing the repository.xml. But catching SAXParseException (a subclass) allows access to column and line numbers of the problem. So also catch this exception and add this to the exception message to make it easier to fix errors.

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