You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/08/29 16:10:22 UTC
[jira] Created: (DERBY-1775) Error 2200M is defined in the SQL
standard as 'invalid XML document' and can be used in multiple situations,
not just XMLPARSE
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
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
[jira] Closed: (DERBY-1775) Error 2200M is defined in the SQL
standard as 'invalid XML document' and can be used in multiple situations,
not just XMLPARSE
Posted by "A B (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1775?page=all ]
A B closed DERBY-1775.
----------------------
Changes in trunk and 10.2 and no further comments, so closing the 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.6, 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: A B
> Priority: Minor
> Fix For: 10.2.1.6, 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
[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
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1775?page=all ]
Mike Matrigali updated DERBY-1775:
----------------------------------
Fix Version/s: 10.2.1.0
marking it a candidate for merge to 10.2
> 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
[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
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ 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
[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
Posted by "A B (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1775?page=all ]
A B updated DERBY-1775:
-----------------------
Assignee: A B
Derby Info: [Patch Available]
> 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
> 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
[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
Posted by "A B (JIRA)" <de...@db.apache.org>.
[ 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
[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
Posted by "A B (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1775?page=all ]
A B updated DERBY-1775:
-----------------------
Attachment: d1775_v2.patch
Thank you for committing the DERBY-1772 patch (and the DERBY-1776 patch, as well!), Mike. I'm attaching a new patch for this issue that resolves the conflict with DERBY-1772. I applied the patch and ran xmlSuite on Windows 2000 (ibm142) with no failures.
> 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
> 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
[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
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1775?page=all ]
Mike Matrigali updated DERBY-1775:
----------------------------------
I committed derby-1772, could you regenerate a new updated patch for this issue to resolve the conflict detailed in the comments above?
> 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
> 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
[jira] Resolved: (DERBY-1775) Error 2200M is defined in the SQL
standard as 'invalid XML document' and can be used in multiple situations,
not just XMLPARSE
Posted by "A B (JIRA)" <de...@db.apache.org>.
[ 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