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 bu...@apache.org on 2003/07/09 18:56:08 UTC
DO NOT REPLY [Bug 21179] -
xsd:include does not work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21179>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21179
xsd:include does not work
------- Additional Comments From mrglavas@apache.org 2003-07-09 16:56 -------
In order for the parser to resolve URIs of external entities, you need to
specify a system ID for the InputSource you return from the EntityResolver.
Without a system ID, how can the parser know what context to use to resolve
URIs? The fallback when no information is supplied by the user is to use the
user's current directory (on their file system) as a base, but this is really
just a stab in the dark. If an entity is located somewhere else, the user is
responsible for providing the base URI, meaning you must call
InputSource.setSystemId().
Given the above point, what behaviour does the parser have that you still
disagree with?
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org