Validation questions

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

Validation questions

Validation questions

2003-01-20 - By Kiran Bhumana

1) Can I pass the schema locations programmatically and not have them at
all in the xml file ?
As per what I gathered, I thought we could, but it does not recognize
the schema.
Only when I specify the schema location in the xml, will it try to parse
against the file

xsi:schemaLocation="http://schemas.xmlsoap.org/ws/2002/07/business-proce
ss/ http://schemas.xmlsoap.org/ws/2002/07/business-process.xsd">

parser.setProperty("http://apache.org/xml/properties/schema/external-sch
emaLocation", "http://schemas.xmlsoap.org/ws/2002/07/business-process/
http://schemas.xmlsoap.org/ws/2002/07/business-process.xsd");

2) Why does it not recognize the following schema definition? I can view
it through explorer. (This same thing works fine with another xsd, per
say, wsdl.xsd)

[Warning]:6:139: schema_reference.4: Failed to read schema document
'http://schemas.x
mlsoap.org/ws/2002/07/business-process.xsd', because 1) could not find
the document;
2) the document could not be read; 3) the root element of the document
is not <xsd:sc
hema>.

Thanks,
Kiran.

-----Original Message-----
From: Kiran Bhumana
Sent: Monday, January 20, 2003 3:49 PM
To: xerces-j-user@(protected)
Subject: RE: another Validation question

So you are suggesting that I define my own xsd file and validate the
instance against it ?

-----Original Message-----
From: Jeff Greif [mailto:jgreif@(protected)]
Sent: Sunday, January 19, 2003 11:42 PM
To: xerces-j-user@(protected)
Subject: Re: another Validation question

Since you are validating the document against the wsdl schema, it must
conform to the WSDL schema. The root element, <definitions> must have
element content of
<documentation>?,<import>* <types>? ,<message>*,<portType>*,<binding>*,
<service>* (and, in WSDL 1.2, <serviceType>*). No other element content
is permitted. At least one content element other than documentation
must be present. The various elements allowed as content may contain
extension elements (outside the wsdl namespace) in certain parts of
their content.

<import> is used to access either datatypes or wsdl elements (those
listed above) held in other files. In wsdl 1.2, no imported item may be
in the targetNamespace of the wsdl definitions while wsdl 1.1 is looser.
When <import> specifies a namespace, this means it is legal to refer to
components from that namespace in the importing document. The schema
processor must also be able to find the declarations of those
references, and uses the schema locations for this purpose (or a
location attribute specified in <import>).

Jeff

>>>>
I have defined "slt" in the wsdl file.

[Error]:20:40: cvc-complex-type.2.4.a: Invalid content starting with
element 'slt:ser
viceLinkType'. The content must match
'(((("http://schemas.xmlsoap.org/wsdl/":documen
tation){0-1}),((WC[##other:"http://schemas.xmlsoap.org/wsdl/"]){0-UNBOUN
DED})),((("ht
tp://

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft
-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1=
"urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC
-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 10">
<meta name=Originator content="Microsoft Word 10">
<link rel=File-List href="cid:filelist.xml@(protected)">
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="time"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="date"/>

<style>

</style>

</head>

<body bgcolor=white lang=EN-US link=blue vlink=purple style='tab-interval:.5in'>

<div class=Section1>

<o:p> </o:p>

1) Can I pass the schema locations programmatically and not
have them at all in the xml file ?<o:p></o:p>

   As per
what I gathered, I thought we could, but it does not recognize the schema.<o:p>
</o:p>

Only when I specify the schema location in the xml, will it
try to parse against the file<o:p></o:p>

<o:p> </o:p>

  xsi:schemaLocation="http://schemas
.xmlsoap.org/ws/2002/07/business-process/
http://schemas.xmlsoap.org/ws/2002/07/business-process.xsd"><o:p></o:p>


<o:p> </o:p>

parser.setProperty("http://apache.org/xml/properties/schema/external
-schemaLocation",
"http://schemas.xmlsoap.org/ws/2002/07/business-process/
http://schemas.xmlsoap.org/ws/2002/07/business-process.xsd");<o:p></o:p>

<o:p> </o:p>

2) Why does it not recognize the following schema definition?
I can view it through explorer. (This same thing works fine with another xsd,
per
say, wsdl.xsd)<o:p></o:p>

<o:p> </o:p>

[Warning]:6:139: schema_reference.4:
Failed to read schema document 'http://schemas.x<o:p><
/o:p>

mlsoap.org/ws/2002/07
/business-process.xsd', because 1) could not find the document;<o:p></o:p>


2) the document
could not be read; 3) the root element of the document is not <xsd:sc<o:p><
/o:p>

hema
>.<o:p></o:p>

<o:p> </o:p>

Thanks,<o:p></o:p>

Kiran.<o:p></o:p>

<o:p> </o:p>

-----Original Message----- 
From: Kiran Bhumana 
Sent: <st1:date
Month="1" Day="20" Year="2003">Monday, January 20, 2003</st1:date>
 <st1:time
Hour="15" Minute="49">3:49 PM</st1:time>
 
To: xerces-j-user@(protected)
 
Subject: RE: another Validation
question

<o:p> </o:p>


So you are suggesting
that I define my own xsd file and validate the instance against it ?<o:p></o:p>



<o:p> </o:p>

-----Original Message----- 
From: Jeff Greif
[mailto:jgreif@(protected)] 
Sent: <st1:date
Month="1" Day="19" Year="2003">Sunday, January 19, 2003</st1:date>
 <st1:time
Hour="23" Minute="42">11:42 PM</st1:time>
 
To: xerces-j-user@(protected)
 
Subject: Re: another Validation
question<o:p></o:p>

<o:p> </o:p>

<div>

Since you are validating the
document against the wsdl schema, it must conform to the WSDL schema.  The
root element, <definitions> must have element content of<o
:p></o:p>

</div>

<div>

<documentation>?,<import
>*
<types>? ,<message>*,<portType>*,<binding>*,
<service>* (and, in WSDL 1.2, <serviceType>*).  No other
element content is permitted.  At least one content element other than
documentation must be present.  The various elements allowed as content
may contain extension elements (outside the wsdl namespace) in certain parts of
their content.<o:p></o:p>

</div>

<div>

 <o:p></o:p>

</div>

<div>

<import> is used to access
either datatypes or wsdl elements (those listed above) held in other
files.  In wsdl 1.2, no imported item may be in the targetNamespace of the
wsdl definitions while wsdl 1.1 is looser. When <import>
specifies a namespace, this means it is legal to refer to components from that
namespace in the importing document.  The schema processor must also be
able to find the declarations of those references, and uses the schema locations
for this purpose (or a location attribute specified in <import>).<o:p></o:p>

</div>

<div>

 <o:p></o:p>

</div>

<div>

Jeff<o:p></o:p>

</div>

<div>

 <o:p></o:p>

</div>

<div>

 >
>>><o:p></o:p>

I have defined
"slt" in the wsdl file.<o:p></o:p>

<o:p> </o:p>


[Error]:<st1:time
Hour="20" Minute="40">20:40</st1:time>: cvc-complex-type.2.4.a: Invalid content
starting with element 'slt:ser<o:p></o:p>

viceLinkType'.
The content must match '(((("http://schemas.xmlsoap.org/wsdl/"
:documen<o:p></o:p>

tation){0-1}),(
(WC[##other:"http://schemas.xmlsoap.org/wsdl/"]){0-UNBOUNDED})),(((
"ht<o:p></o:p>

tp://<o:p></o:p>


<o:p> </o:p>

</div>

</div>

</body>

</html>