You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "elharo (JIRA)" <xe...@xml.apache.org> on 2005/12/19 14:23:30 UTC
[jira] Created: (XERCESJ-1124) Nonspecific schema error message
Nonspecific schema error message
--------------------------------
Key: XERCESJ-1124
URL: http://issues.apache.org/jira/browse/XERCESJ-1124
Project: Xerces2-J
Type: Improvement
Components: XML Schema API
Versions: 2.7.1
Reporter: elharo
Priority: Minor
The following error message recently popped out of Xerces:
[Warning] :5:2: schema_reference.4: Failed to read schema document
'cml0.xsd', because 1) could not find the document; 2) the document
could not be read; 3) the root element of the document is not <xsd:schema>.
This is unhelpful. The reason the reading failed is either 1, or 2, or 3. Xerces should distinguish all three cases and only use the error message that reflects the actual problem.
Grepping the source this string appears in XMLSchemaMessages.properties. I'm not sure where in the Java code the distinction needs to be made.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: [jira] Created: (XERCESJ-1124) Nonspecific schema error message
Posted by "M.Nadhiya" <na...@tataelxsi.co.in>.
elharo (JIRA <xerces-j-dev <at> xml.apache.org> writes:
> Hi
I am currently working on this and i am facing the same problem.
can you please tell me what can i do for that?
thnks in advance
M.Nadhiya
> Nonspecific schema error message
> --------------------------------
>
> Key: XERCESJ-1124
> URL: http://issues.apache.org/jira/browse/XERCESJ-1124
> Project: Xerces2-J
> Type: Improvement
> Components: XML Schema API
> Versions: 2.7.1
> Reporter: elharo
> Priority: Minor
>
> The following error message recently popped out of Xerces:
>
> [Warning] :5:2: schema_reference.4: Failed to read schema document
> 'cml0.xsd', because 1) could not find the document; 2) the document
> could not be read; 3) the root element of the document is not <xsd:schema>.
>
> This is unhelpful. The reason the reading failed is either 1, or 2, or 3.
Xerces should distinguish all three
> cases and only use the error message that reflects the actual problem.
>
> Grepping the source this string appears in XMLSchemaMessages.properties. I'm
not sure where in the Java
> code the distinction needs to be made.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Updated: (XERCESJ-1124) Nonspecific schema error message
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich updated XERCESJ-1124:
------------------------------------------
Affects Version/s: 2.9.1
2.9.0
2.8.1
2.8.0
Fix Version/s: 2.10.0
> Nonspecific schema error message
> --------------------------------
>
> Key: XERCESJ-1124
> URL: https://issues.apache.org/jira/browse/XERCESJ-1124
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema 1.0 Structures
> Affects Versions: 2.7.1, 2.8.0, 2.8.1, 2.9.0, 2.9.1
> Reporter: elharo
> Assignee: Michael Glavassevich
> Priority: Minor
> Fix For: 2.10.0
>
> Time Spent: 0.25h
> Remaining Estimate: 0h
>
> The following error message recently popped out of Xerces:
> [Warning] :5:2: schema_reference.4: Failed to read schema document
> 'cml0.xsd', because 1) could not find the document; 2) the document
> could not be read; 3) the root element of the document is not <xsd:schema>.
> This is unhelpful. The reason the reading failed is either 1, or 2, or 3. Xerces should distinguish all three cases and only use the error message that reflects the actual problem.
> Grepping the source this string appears in XMLSchemaMessages.properties. I'm not sure where in the Java code the distinction needs to be made.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Resolved: (XERCESJ-1124) Nonspecific schema error message
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich resolved XERCESJ-1124.
-------------------------------------------
Resolution: Fixed
The actual cause is an IOException which Xerces was swallowing. This is now retrievable from SAXException.getException() for applications which want more information about the type failure that occurred when trying to read the schema document.
> Nonspecific schema error message
> --------------------------------
>
> Key: XERCESJ-1124
> URL: https://issues.apache.org/jira/browse/XERCESJ-1124
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema API
> Affects Versions: 2.7.1
> Reporter: elharo
> Assignee: Michael Glavassevich
> Priority: Minor
>
> The following error message recently popped out of Xerces:
> [Warning] :5:2: schema_reference.4: Failed to read schema document
> 'cml0.xsd', because 1) could not find the document; 2) the document
> could not be read; 3) the root element of the document is not <xsd:schema>.
> This is unhelpful. The reason the reading failed is either 1, or 2, or 3. Xerces should distinguish all three cases and only use the error message that reflects the actual problem.
> Grepping the source this string appears in XMLSchemaMessages.properties. I'm not sure where in the Java code the distinction needs to be made.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Issue Comment Edited: (XERCESJ-1124) Nonspecific schema
error message
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700592#action_12700592 ]
Michael Glavassevich edited comment on XERCESJ-1124 at 4/19/09 9:34 AM:
------------------------------------------------------------------------
The actual cause is an IOException which Xerces was swallowing. This is now retrievable from SAXException.getException() for applications which want more information about the type of failure that occurred when trying to read the schema document.
was (Author: mrglavas@ca.ibm.com):
The actual cause is an IOException which Xerces was swallowing. This is now retrievable from SAXException.getException() for applications which want more information about the type failure that occurred when trying to read the schema document.
> Nonspecific schema error message
> --------------------------------
>
> Key: XERCESJ-1124
> URL: https://issues.apache.org/jira/browse/XERCESJ-1124
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema API
> Affects Versions: 2.7.1
> Reporter: elharo
> Assignee: Michael Glavassevich
> Priority: Minor
>
> The following error message recently popped out of Xerces:
> [Warning] :5:2: schema_reference.4: Failed to read schema document
> 'cml0.xsd', because 1) could not find the document; 2) the document
> could not be read; 3) the root element of the document is not <xsd:schema>.
> This is unhelpful. The reason the reading failed is either 1, or 2, or 3. Xerces should distinguish all three cases and only use the error message that reflects the actual problem.
> Grepping the source this string appears in XMLSchemaMessages.properties. I'm not sure where in the Java code the distinction needs to be made.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Updated: (XERCESJ-1124) Nonspecific schema error message
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich updated XERCESJ-1124:
------------------------------------------
Component/s: (was: XML Schema API)
XML Schema 1.0 Structures
> Nonspecific schema error message
> --------------------------------
>
> Key: XERCESJ-1124
> URL: https://issues.apache.org/jira/browse/XERCESJ-1124
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema 1.0 Structures
> Affects Versions: 2.7.1
> Reporter: elharo
> Assignee: Michael Glavassevich
> Priority: Minor
> Time Spent: 0.25h
> Remaining Estimate: 0h
>
> The following error message recently popped out of Xerces:
> [Warning] :5:2: schema_reference.4: Failed to read schema document
> 'cml0.xsd', because 1) could not find the document; 2) the document
> could not be read; 3) the root element of the document is not <xsd:schema>.
> This is unhelpful. The reason the reading failed is either 1, or 2, or 3. Xerces should distinguish all three cases and only use the error message that reflects the actual problem.
> Grepping the source this string appears in XMLSchemaMessages.properties. I'm not sure where in the Java code the distinction needs to be made.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Assigned: (XERCESJ-1124) Nonspecific schema error message
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich reassigned XERCESJ-1124:
---------------------------------------------
Assignee: Michael Glavassevich
> Nonspecific schema error message
> --------------------------------
>
> Key: XERCESJ-1124
> URL: https://issues.apache.org/jira/browse/XERCESJ-1124
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema API
> Affects Versions: 2.7.1
> Reporter: elharo
> Assignee: Michael Glavassevich
> Priority: Minor
>
> The following error message recently popped out of Xerces:
> [Warning] :5:2: schema_reference.4: Failed to read schema document
> 'cml0.xsd', because 1) could not find the document; 2) the document
> could not be read; 3) the root element of the document is not <xsd:schema>.
> This is unhelpful. The reason the reading failed is either 1, or 2, or 3. Xerces should distinguish all three cases and only use the error message that reflects the actual problem.
> Grepping the source this string appears in XMLSchemaMessages.properties. I'm not sure where in the Java code the distinction needs to be made.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org