OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Xerces1.4.4 and xerces 2.x

[ Lists Home | Date Index | Thread Index ]

Hello,

You may think that this is not the mailing list from xerces but it is
down, this is the best I could find.

Here i sthe deal. Here are two xsds.

First

<xs:schema targetNamespace="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:response="http://myhost/TruckTrace";
xmlns:request="http://myhost/TruckTrace"; elementFormDefault="qualified"
attributeFormDefault="qualified">
	<xs:import namespace="http://myhost/TruckTrace";
schemaLocation="TruckTraceRequest.xsd"/>
	<xs:import namespace="http://myhost/TruckTrace";
schemaLocation="TruckTraceResponse.xsd"/>
	<xs:element name="Envelope">
		<xs:complexType>
			<xs:sequence>
				<xs:element name="Header"
type="SOAP-ENV:HeaderType" form="qualified" minOccurs="0"/>
				<xs:element name="Body"
form="qualified">
					<xs:complexType>
						<xs:choice>
							<xs:element
ref="request:truckEnqui"/>
							<xs:element
ref="response:truckResponse"/>
							<xs:element
name="Fault" type="SOAP-ENV:FaultType"/>
						</xs:choice>
					</xs:complexType>
				</xs:element>
			</xs:sequence>
			<xs:attribute name="encodingStyle"
use="optional" fixed="http://schemas.xmlsoap.org/soap/encoding/"/>
		</xs:complexType>
	</xs:element>
	<xs:complexType name="HeaderType">
		<xs:sequence>
			<xs:any namespace="##other"
processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
		</xs:sequence>
		<xs:anyAttribute namespace="##other"
processContents="lax"/>
	</xs:complexType>
	<xs:complexType name="FaultType">
		<xs:sequence>
			<xs:element name="faultcode" type="xs:QName"/>
			<xs:element name="faultstring"
type="xs:string"/>
			<xs:element name="faultfactor" type="xs:anyURI"
minOccurs="0"/>
			<xs:element name="detail" minOccurs="0">
				<xs:complexType>
					<xs:sequence>
						<xs:any
namespace="##any" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
					</xs:sequence>
					<xs:anyAttribute
namespace="##any" processContents="lax"/>
				</xs:complexType>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
</xs:schema>


and second


<xs:schema targetNamespace="http://myhost/TruckTrace";
xmlns="http://myhost/TruckTrace";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
elementFormDefault="unqualified" attributeFormDefault="unqualified">
	<xs:element name="truckResponse">
		<xs:complexType>
			<xs:sequence>
				<xs:element name="result"
type="resultType" form="unqualified" minOccurs="0"
maxOccurs="unbounded"/>
			</xs:sequence>
			<xs:attribute name="resultNumber" type="xs:int"
use="required" form="unqualified"/>
		</xs:complexType>
	</xs:element>
	<xs:complexType name="resultType">
	.....
	</xs:complexType>
</xs:schema>


With our words and what we understood, the first is referencing the
second.

With xerces 1.4.4, the parser that we implemented does its job
correctly. It has the following features :

http://apache.org/xml/features/validation/schema-full-checking
http://xml.org/sax/features/validation
http://apache.org/xml/features/validation/schema
http://xml.org/sax/features/namespaces


But with xerces 2.2.1 we keep getting this error :
"src-resolve: Cannot resolve the name 'response:truckResponse' to a(n)
element declaration component."

We have no idea where the problem could be, so if you could help....

Regards

Mederick




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS