db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1775) Error 2200M is defined in the SQL standard as 'invalid XML document' and can be used in multiple situations, not just XMLPARSE
Date Tue, 19 Sep 2006 17:15:27 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1775?page=all ]

A B updated DERBY-1775:
-----------------------

    Attachment: d1775_v1.patch

Attaching a patch that does the following:

 1. Updates the 2200M message text to be more generic,
    as suggested in the description of this issue.

 2. Replaces "see next exception" with the in-lined 
    error message while continuing to do exception
    chaining as usual.

 3. Also replaces "see next exception" with in-line
    error messages for a couple of other SQL/XML
    errors--namely UNEXPECTED_XML_ERROR and
    XML_QUERY_ERROR.

I ran xmlSuite on Windows 2000 using ibm142 and all tests passed.

NOTE: This patch has a one-line conflict with the patch posted for DERBY-1772.  When either
patch is committed, the other will have to be regenerated to resolve the conflict.

> Error 2200M is defined in the SQL standard as 'invalid XML document' and can be used
in multiple situations, not just XMLPARSE
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1775
>                 URL: http://issues.apache.org/jira/browse/DERBY-1775
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.2.1.0, 10.3.0.0
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>         Attachments: d1775_v1.patch
>
>
> Derby's text for 2200M is as below, probably should start out being more generic. Also
based upon past error messages like this ('see next for details') it's probably best to include
the text of the next message in the first, while continuing to chain them.
> Consider replacing:
> ERROR 2200M: Failed to parse XMLPARSE operand; see next exception for details.
> ERROR XJ001: Java exception: 'Element type "idtwo" must be followed by either at
> tribute specifications, ">" or "/>".: org.xml.sax.SAXException'.
> with
> ERROR 2200M: Invalid XML DOCUMENT : Element type "idtwo" must be followed by either at
> tribute specifications, ">" or "/>".: org.xml.sax.SAXException'.
> ERROR XJ001: Java exception: 'Element type "idtwo" must be followed by either at
> tribute specifications, ">" or "/>".: org.xml.sax.SAXException'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message