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 2002/05/03 19:54:52 UTC
DO NOT REPLY [Bug 8786] New: -
Unable to setProperty (external-schemaLocation) with schemaLocations containing spaces
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=8786>.
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=8786
Unable to setProperty (external-schemaLocation) with schemaLocations containing spaces
Summary: Unable to setProperty (external-schemaLocation) with
schemaLocations containing spaces
Product: Xerces2-J
Version: 2.0.1
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: DOM
AssignedTo: xerces-j-dev@xml.apache.org
ReportedBy: mdiiorio@iss.net
When calling DOMParser.setProperty
( "http://apache.org/xml/properties/schema/external-schemaLocation", <string of
schemaLocations> );
If any of the schemaLocations contain spaces (even if they're wrapped in
quotes) - the namespace/location pairs are incorrectly parsed: the string is
tokenized with whitespace delimeters with no regard for the quotes. This makes
it impossible to use a schema file who's path contains spaces. For example: a
schemaLocation string of:
http://www.foobar.com "file:/c:/Program
Files/MyCompany/MyApplication/schemas/mySchema.xsd"
is tokenized to 3 separate tokens:
-- http://www.foobar.com --
-- "file:/c:/Program --
-- Files/MyCompany/MyApplication/schemas/mySchema.xsd" --
Looking at the source, I *think* this parsing code resides in
XSDHandler.LocationResolver.reset().
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org