Invalid anyURI type - A Bug Or Intended to Be

Subjects

•	Home
•	VOTE Move XML Commons to Xerces
•	Commented: (XERCESJ 589) Bug with pattern restriction on long strings
•	: Xerces J 2 8 1 Release on Wednesday, September 13th
•	: Xerces J 2 9 0 Release on Wednesday, November 22nd
•	Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
•	Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
•	Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
•	Some consideration about the xerces DOM implementation
•	Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
•	Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
•	retain exception stack traces
•	Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
•	Future of NekoHTML
•	Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
•	DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
•	: xml commons external 1 3 04 Release on Wednesday, November 22nd
•	Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
•	XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
•	First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
•	: xml commons resolver 1 2 Release on Wednesday, November 22nd
•	Typo in RangeToken java Please check
•	Validator features
•	java lang ClassCastException when adopting Node
•	using the org apache xerces impl xs identity package
•	Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
•	Problem with ref attributes and schema validation
•	Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
•	Performance problem under load Xerces with Weblogic 9 x
•	remove ignored memory allocation
•	Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
•	Commented: (XERCESJ 977) Null pointer exception during DOM parsing
•	Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
•	Commented: (XERCESJ 1201) Initial contribution for StAX Event API
•	Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
•	Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
•	Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
•	Updated: (XERCESJ 589) Bug with pattern restriction on long strings
•	StackOverflow
•	xerces Range unnecessarily not garbage collectable if not detached
•	Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
•	Bug in xs:redefine
•	Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
•	Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
•	Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
•	Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
•	Google Summer of Code 2007
•	Xerces J and XInclude relative path issue
•	Assigned: (XERCESJ 206) Stack overflow when using a schema validation
•	Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
•	Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
•	non overriding equals methoda
•	Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
•	Xerces AS3 port
•	Updated: (XERCESJ 325) Regular Expression; Pattern "\| " clause order de
•	Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
•	Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
•	Created: (XERCESJ 1124) Nonspecific schema error message
•	a bug in xerces
•	Updated: (XERCESJ 1201) Initial contribution for StAX Event API
•	Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report

Links

Home

Oracle database error code

Invalid anyURI type - A Bug Or Intended to Be

Invalid anyURI type - A Bug Or Intended to Be

2003-03-28 - By Cao, Dekun

Reply: 1 2 3 4 5 6

But this will cause some problems if the schema file is located in a
directory which contains a white space, such as on Windows. Based on
"Uniform Resource Identifiers (URI): Generic Syntax"
http://www.ietf.org/rfc/rfc2396.txt, white space is NOT allowed in URI. I
have verified that white space in schema file path doesn't work with the
code at the end of this message.

My Question here is: Is this a bug or it is intended to do that?

Thank you very much.

Dekun

import org.apache.xerces.parsers.DOMParser;
import org.w3c.dom.Document;
import org.xml.sax.InputSource;

/**
* Example tested with Xerces 2.0.0
*/
public class MyDomTest
{
public static void main(String[] args) throws Exception
{
// get hold of a DOM parser
DOMParser parser = new DOMParser();

// turn on schema validation ( note need to set both sax and dom
validation )
parser.setFeature("http://apache.org/xml/features/validation/schema",
true );

// The following path works
// String xsdFile = new String("S:/myFile.xsd");

// The following path doesn't works
String xsdFile = new String("C:\\Program Files\\myFile.xsd"); // NOT
working

parser.setProperty("http://apache.org/xml/properties/schema/external-noNames
paceSchemaLocation"
, xsdFile);

// parse the document
InputSource is = new InputSource( "S:\\myMsgs_en.xml" );
parser.parse( is );

// get the w3c document
Document doc = parser.getDocument();
}
}

-----Original Message-----
From: Sandy Gao [mailto:sandygao@(protected)]
Sent: Friday, March 28, 2003 1:40 PM
To: xerces-j-user@(protected)
Subject: Re: Invalid anyURI type

No, "M:\software_development\xml\xsd\custom.xsd" is not a URI.
"file:///M:/software_development/xml/xsd/custom.xsd" is.

Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
sandygao@(protected)

"Thropp, Shawn"

<thropp@(protected) To:
"'xerces-j-user@(protected)'" <xerces-j-user@(protected)>
g> cc:

Subject: Invalid anyURI type

03/28/2003 01:08

PM

Please respond to

xerces-j-user

In the past I have been trying to set the external-schemaLocation Property
and I understand there have been several bugs reported. I am not sure if
the particular problem that I am having is a bug in Xerces-J or the way I
am
trying to create and use a DOM Parser and external-scheamLocation property.

In our implementation I set the external-schemaLocation property to a
string
that contains the all of the namespaces and XSDs to use (in the proper
format). For a sanity check, I get the extenal-schemaLocation property
after I set to verify it got set correctly. It seems to be setting it
correctly.

When that actual parser begins doing its job, I receive the following
error:
FAILED: cvc-datatype-valid.1.2.1:
'M:\software_development\xml\xsd\custom.xsd' is not a valid 'anyURI' value.
line: -1, col: -1

The XSDs all exist locally on my system. Is the string, in the error
message, a valid URI? Or is there a bug with the handling of the
external-schemaLocation property?

Thanks for the help
Schawn

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)

This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so. Thank you.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: Invalid anyURI type - A Bug Or Intended to Be</TITLE>
</HEAD>
<BODY>

But this will cause some problems if the schema file is located
in a directory which contains a white space, such as on Windows. Based on &quot
;Uniform Resource Identifiers (URI): Generic Syntax" <A HREF="http://www
.ietf.org/rfc/rfc2396.txt" TARGET="_blank">http://www.ietf.org/rfc/rfc2396.txt<
/A>, white space is NOT allowed in URI. I have verified that white space in
schema file path doesn't work with the code at the end of this message.

My Question here is: Is this a bug or it is intended to do that
?


Thank you very much.


Dekun

 

import org.apache.xerces.parsers.DOMParser;
 import org.w3c.dom.Document;
 import org.xml.sax.InputSource;


/**
  * Example tested with Xerces 2.0.0
  */
 public class MyDomTest
 {
   public static void main(String[] args) throws Exception

   {
     // get hold of a DOM parser
     DOMParser parser = new DOMParser();


    // turn on schema validation ( note need to
set both sax and dom validation )
     parser.setFeature("<A HREF="http:/
/apache.org/xml/features/validation/schema" TARGET="_blank">http://apache.org
/xml/features/validation/schema</A>", true );


    // The following path works
 //      String xsdFile = new String(
"S:/myFile.xsd");


    // The following path doesn't works
         String xsdFile =
new String("C:\\Program Files\\myFile.xsd"); // NOT working
              
          
         parser.setProperty(
"<A HREF="http://apache.org/xml/properties/schema/external
-noNamespaceSchemaLocation" TARGET="_blank">http://apache.org/xml/properties
/schema/external-noNamespaceSchemaLocation</A>"
         , xsdFile);


    // parse the document
     InputSource is = new InputSource( "S:\
\myMsgs_en.xml" );
     parser.parse( is );


    // get the w3c document
     Document doc = parser.getDocument();
   }
 }

 

-----Original Message-----
 From: Sandy Gao [<A HREF="mailto:sandygao@(protected)">mailto
:sandygao@(protected)</A>]
 Sent: Friday, March 28, 2003 1:40 PM
 To: xerces-j-user@(protected)
 Subject: Re: Invalid anyURI type

 

No, "M:\software_development\xml\xsd\custom.xsd" is
not a URI.
 "<A HREF="file:///M:/software_development/xml/xsd/custom
.xsd" TARGET="_blank">file:///M:/software_development/xml/xsd/custom.xsd</A>
" is.


Sandy Gao
 Software Developer, IBM Canada
 (1-905) 413-3255
 sandygao@(protected)

 
 

          
             
             
             
             
             
             
             
             
              

          
            "Thropp,
Shawn"           
             
             
             
             
             
             
  

          
            <thropp
@(protected)        To:    
   "'xerces-j-user@(protected)'" <xerces-j-user@(protected)
.apache.org>        

          
            g> 
             
         cc:    
             
             
             
             
             
         

          
             
             
           Subject: 
Invalid anyURI type          
             
             
             
   

          
            03/28/2003 01
:08            &nbsp
;             
             
             
             
             
            

          
            PM &nbsp
;             
             
             
             
             
             
             
           

          
            Please
respond to           
             
             
             
             
             
             


          
            xerces-j-user
             
             
             
             
             
             
             
  

          
             
             
             
             
             
             
             
             
              

          
             
             
             
             
             
             
             
             
              
 
 

In the past I have been trying to set the external
-schemaLocation Property
 and I understand there have been several bugs reported. 
I am not sure if
 the particular problem that I am having is a bug in Xerces-J
or the way I
 am
 trying to create and use a DOM Parser and external
-scheamLocation property.


In our implementation I set the external-schemaLocation
property to a
 string
 that contains the all of the namespaces and XSDs to use (in
the proper
 format).  For a sanity check, I get the extenal
-schemaLocation property
 after I set to verify it got set correctly.  It seems to
be setting it
 correctly.


When that actual parser begins doing its job, I receive the
following
 error:
 FAILED: cvc-datatype-valid.1.2.1:
 'M:\software_development\xml\xsd\custom.xsd' is not a valid
'anyURI' value.
 line: -1, col: -1


The XSDs all exist locally on my system.  Is the string,
in the error
 message, a valid URI?  Or is there a bug with the
handling of the
 external-schemaLocation property?


Thanks for the help
 Schawn


---------------------------------------------------------------
------
 To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
.org
 For additional commands, e-mail: xerces-j-user-help@(protected)
.org

 
 
 
 

---------------------------------------------------------------
------
 To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
.org
 For additional commands, e-mail: xerces-j-user-help@(protected)
.org


This message may contain privileged and/or confidential
information.  If you have received this e-mail in error or are not the
intended recipient, you may not use, copy, disseminate or distribute it; do not
open any attachments, delete it immediately from your system and notify the
sender promptly by e-mail that you have done so.  Thank you.

</BODY>
</HTML>