The following issue has been updated:
Updater: Alberto Massari (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Oct 2004 12:49 AM
Changes:
assignee changed from Xerces-C Developers Mailing List
type changed from Bug to New Feature
description changed from I want Xerces to validate documents against
their schema, but I don't
want to depend on documents to contain hardcoded schema locations.
So I implemented an XMLEntityResolver in order to intercept SchemaGrammar
resolutions. However, this does not work, and the XMLEntityResolver is not
asked to resolve the schema namespaces. Validation then fails.
For some reason, it works if (a) you set the XercesSchemaExternalSchema-
Location property to point to random locations (which are being ignored),
and it also works if the document contains an xmi:schemaLocation attribute
for its namespace. I do not want to do either.
Test program, document and schemas attached. Expected output is "document
parsed okay.", preceded by messages from the entityResolver resolving some
SchemaGrammar and SchemaImport namespaces.
Current output is "document error." preceded by messages from the error
handler.
Problem verified with Xerces-C++ 2.5.0 on Windows 2000 / VC++ 6, but it
seems platform independent. to I want Xerces to validate documents against their
schema, but I don't
want to depend on documents to contain hardcoded schema locations.
So I implemented an XMLEntityResolver in order to intercept SchemaGrammar
resolutions. However, this does not work, and the XMLEntityResolver is not
asked to resolve the schema namespaces. Validation then fails.
For some reason, it works if (a) you set the XercesSchemaExternalSchema-
Location property to point to random locations (which are being ignored),
and it also works if the document contains an xmi:schemaLocation attribute
for its namespace. I do not want to do either.
Test program, document and schemas attached. Expected output is "document
parsed okay.", preceded by messages from the entityResolver resolving some
SchemaGrammar and SchemaImport namespaces.
Current output is "document error." preceded by messages from the error
handler.
Problem verified with Xerces-C++ 2.5.0 on Windows 2000 / VC++ 6, but it
seems platform independent.
environment changed from Operating System: All
Platform: All to Operating System: All
Platform: All
priority changed to Blocker
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/XERCESC-1180?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1180
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XERCESC-1180
Summary: Add the possibility of loading a schema by just declaring a namespace
binding
Type: New Feature
Status: Unassigned
Priority: Blocker
Project: Xerces-C++
Components:
Validating Parser (Schema) (Xerces 1.5 or up only)
Versions:
2.5.0
Assignee:
Reporter: Frank Pilhofer
Created: Fri, 19 Mar 2004 8:13 PM
Updated: Mon, 4 Oct 2004 12:49 AM
Environment: Operating System: All
Platform: All
Description:
I want Xerces to validate documents against their schema, but I don't
want to depend on documents to contain hardcoded schema locations.
So I implemented an XMLEntityResolver in order to intercept SchemaGrammar
resolutions. However, this does not work, and the XMLEntityResolver is not
asked to resolve the schema namespaces. Validation then fails.
For some reason, it works if (a) you set the XercesSchemaExternalSchema-
Location property to point to random locations (which are being ignored),
and it also works if the document contains an xmi:schemaLocation attribute
for its namespace. I do not want to do either.
Test program, document and schemas attached. Expected output is "document
parsed okay.", preceded by messages from the entityResolver resolving some
SchemaGrammar and SchemaImport namespaces.
Current output is "document error." preceded by messages from the error
handler.
Problem verified with Xerces-C++ 2.5.0 on Windows 2000 / VC++ 6, but it
seems platform independent.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
