[ http://issues.apache.org/jira/browse/DERBY-1775?page=all ]

A B resolved DERBY-1775.
------------------------

    Resolution: Fixed
    Derby Info:   (was: [Patch Available])

Patch has now been mega-merged to 10.2.  I ran xmlSuite on Windows 2000 with 
ibm142 to make sure all is well, and also manually verified that the changes 
are in.  So I'm setting Fixin, unchecking "Patch Available", and resolving this 
issue.

> 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

        

Reply via email to