db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (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 Wed, 20 Sep 2006 16:33:23 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1775?page=all ]

Mike Matrigali updated DERBY-1775:
----------------------------------

    Fix Version/s: 10.3.0.0

committed the latest patch to the trunk, this can be merged to 10.2.

m1_ibm142:123>svn commit

Sending        java\engine\org\apache\derby\iapi\types\SqlXmlUtil.java
Sending        java\engine\org\apache\derby\iapi\types\XML.java
Sending        java\engine\org\apache\derby\loc\messages_en.properties
Sending        java\testing\org\apache\derbyTesting\functionTests\master\DerbyNet\xml_general.out
Sending        java\testing\org\apache\derbyTesting\functionTests\master\DerbyNetClient\xml_general.out
Sending        java\testing\org\apache\derbyTesting\functionTests\master\xml_general.out
Transmitting file data ......
Committed revision 448258.

> 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
>         Assigned To: A B
>            Priority: Minor
>             Fix For: 10.2.1.0, 10.3.0.0
>
>         Attachments: d1775_v1.patch, d1775_v2.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