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/01/08 07:37:23 UTC

DO NOT REPLY [Bug 15878] New: - schema name in namespace property changed to URI

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=15878>.
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=15878

schema name in namespace property changed to URI

           Summary: schema name in namespace property changed to URI
           Product: Xerces2-J
           Version: 2.2.1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: SAX
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: neil@bluesock.org


When you use the http://apache.org/xml/properties/schema/external-schemaLocation
property (and I imagine the no-namespace one as well, although I didn't try it),
the schema name provided to the property is changed to a URI when presented to
the entity resolver. In other words, if one were to specify the example value
provided in the documentation: "http://www.example.com file_name.xsd", when the
entity resolver is invoked, the provided id would not be file_name.xsd, but
instead something like "file://c:/program files/myApplication/file_name.xsd".
This is a bad thing, since our entity resolver is expecting the schema name to
match what we set on the property value. This conversion to a URI did not used
to occur and is new to this version (or perhaps the one just prior to it).

At the very least, it seems like a feature or property should be introduced to
disable this URI conversion and the documentation should be updated to state the
fact that it occurs. It should also be noted in the backward-compatibility
section of the documentation as this change may very well break older
applications that, like ours, expects the id passed to the entity resolver to
match the id set on the property.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org