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 ji...@apache.org on 2004/04/12 23:27:50 UTC

[jira] Updated: (XERCERJ-485) Setting the external-schemaLocation property does not seem to work

The following issue has been updated:

    Updater: Serge Knystautas (mailto:sergek@lokitech.com)
       Date: Mon, 12 Apr 2004 2:26 PM
    Changes:
             Attachment changed from Test.java
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/XERCERJ-485?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCERJ-485

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCERJ-485
    Summary: Setting the external-schemaLocation property does not seem to work
       Type: Bug

     Status: Resolved
 Resolution: CANNOT REPRODUCE

    Project: Xerces2-J

   Assignee: Xerces-J Developers Mailing List
   Reporter: Constantine Georges

    Created: Mon, 14 Oct 2002 8:07 PM
    Updated: Mon, 12 Apr 2004 2:26 PM
Environment: Operating System: Windows NT/2K
Platform: PC

Description:
Setting the external-schemaLocation property for Xerces 2.2 does not resolve 
schema locations.  Xerces will resolve a schema location if a reference to it 
exists in the instance document that it is validating (via the 
xsi:schemaLocation attribute).  This was observed using both the JAXP and 
native (DOMParser, SAXParser) interfaces.

This was not observed under Xerces 2.1 or Xerces 1.4.4 -- under both libraries, 
setting the schemaLocation property via code worked to resolve locations.

Under all libraries, however, the JAXP interface for isValidating() only seems 
to turn on validation through a DTD grammar, regardless of whether the 
schemaLocation property is set (via code OR via xsi:schemaLocation in the 
instance).  Is this a bug in the JAXP interface implementations, or is this 
functionality expected?


---------------------------------------------------------------------
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org